We started using it for unifi.ui.com and the render performance gain has been massive.
HN user
Ambroos
Software person, with a past in Belgium/Ireland/US, a present in Sweden and future in ???
Yes, in some European countries, although only for a limited time and they never sold well.
Yes. Android Auto and CarPlay still work and you get basic Google Maps functionality without signing in. You can't download additional apps though.
These levels exist since the DSM-5, which is not yet in use everywhere:
The DSM-5 introduced three ASD levels of severity: level 1 (“requiring support”), level 2 (“requiring substantial support”), and level 3 (“requiring very substantial support”).
https://www.autismspeaks.org/levels-of-autism has a good complete overview.
I run our office IT, and WiFi 7 is just better at managing congestion. We have a floor in a busy building and 5Ghz is chaos. 6E is fine, it's just strangely old for a company like Apple.
The lack of WiFi 7 is disappointing. 6E is fine but by now I'd expect 7 in new computers.
The Ollama Mac app has essentially not changed since early 2024: https://github.com/ollama/ollama/commits/main/macapp
Has anyone been able to confirm if the macOS 26.1 developer beta is affected? I updated to it pretty quickly and haven't been able to reproduce the lag on it.
It's on both. Apple should probably have caught this in beta considering how widespread Electron apps are, and have worked with Electron to fix it or they should've worked around it (which Microsoft would probably have done).
This might be a good time to remind you that her Vulnicura VR album (that the video you linked to is from) has just been remastered and rereleased. Available on Quest 3 (https://www.meta.com/en-gb/experiences/9760145800676411/) and Vision Pro (https://apps.apple.com/us/app/bj%C3%B6rk-vulnicura-vr-remast...). It's one of my favourite ever albums and I really need to find a friend with a Quest 3/Vision Pro, I have never gotten to experience the VR videos.
It's IEC 62196-2 Type 2 (Mennekes) and CCS2 in Europe. J1772 is the North American standard that is used in CCS1.
Power generated on a train is probably significantly more expensive than power you can pull from the grid. Most of Amtrak's network does not have power so I assume they rely on generators on the train.
Almost all of the other things you want to get rid of are legal requirements in some regions. Auto start-stop is generally to meet emissions targets. European safety regulations have made all of the following required on all new vehicles sold since mid 2024: AEB detecting cars/pedestrians/cyclists, intelligent speed assist, lane departure assist, reversing camera or sensors, drowsiness warning and a few others. For any car or platform that will at some point end up on the European market you can thus expect manufacturers to make all of these standard.
There's a cost attached to them, but it was decided that that cost is worth the significant benefits in road safety for both the people in the vehicle and the people around the vehicle.
DPI happens on a UniFi Gateway. That could be the same hardware as the controller when it's a UniFi device like a Dream Machine/Dream Router, but it doesn't have to be. The Gateway will do the DPI and report the numbers to the controller where they are stored and displayed.
The last few years it's been tougher and tougher to get them. Even in Europe you can now only buy them directly from Sony, and Amazon in a few countries. Sony is not selling them via any other retailers or operators at all from this year onwards.
I still really like Sony phones. Excellent hardware. They have no online services they are trying to push, they just want you to buy their phones. As a result, the stock software is very clean Google Android without much extra. But they're not available in every region, and quite expensive. Used to have very short software support but now they do 4 major Android version updates / 6 years of security updates.
You get no ecosystem benefits though, it's really just plain Android.
We all appreciate the data, but seriously, get a hobby that doesn't involve arguing with a car's GPS.
Brutal, and very accurate. This is great!
That depends on how they're set up. There is no real protocol difference between MasterCard and Visa debit vs credit. Delhaize in Belgium also uses them and you can definitely use all types of credit cards with them (at least Visa/MC and even AmEx).
I wonder if this is a Swedish thing. I recently moved to a newly built apartment in Stockholm (as a non-Swede). All spots to put a ceiling light come with a hook and DCL socket, so it makes it super easy to swap lamps.
Internally at Facebook you could also just call React components from XHP. Not very relevant on what you see on Facebook now as a user, but in older internal tools built with XHP it made it very easy to just throw in React components.
When you'd annotate a React component with ReactXHP (if I remember correctly), some codegen would generate an equivalent XHP components that takes the same props, and can just be used anywhere in XHP. It worked very well when I last used it!
Slightly less related but still somewhat, they have an extension to GraphQL as well that allows you to call/require React components from within GraphQL. If you look at a random GraphQL response there's a good chance you will see things like `"__dr": "GroupsCometHighlightStoryAlbumAttachmentStyle.react"`. I never looked into the mechanics of how these worked.
I'm far from an expert, but what is most likely is:
- The underlying firmware for the Marvell WiFi controller that Sony provided when they updated the PSP to support WPA (with AES) also supports WPA2 (with AES).
- Sony never set it up on the userspace side, perhaps for stability reasons or because there was no demand and they preferred playing it safe.
- The patches swap out the userspace bits to talk WPA AES with the ones for a WPA2 AES. The difference isn't huge, it's mostly changing data in some management frames and configuring the key exchange differently.
It's very impressive that that developer found the right things to patch, with the right values.
Looks like it has been in the works for a while.
UniFi access points run OpenWRT. The latest beta releases for the U7 series for example is on OpenWRT 23.05.
Audio is tiny compared to video (and even images), especially for podcasts, think ~1MB/minute. And they compress well if you want them to be smaller. High quality video (think 4K HDR) can quite comfortably be over 1MB per second.
I assume they don't want to become a file sharing website, but hosting a podcast is relatively easy on the bandwidth requirements.
If you can run your application on Cloudflare Pages / Workers with Cloudflare's storage/DB things, it really gets dirt cheap (if not free) and very fast. And even without that, Cloudflare's caching CDN is very good, very cheap and very easy.
Apps still don't have system level access to anything, so no. iPhone apps can't automatically run in the background, run on boot or just access random data from random apps. If they can it'd be an exploit, and while the App Store gives you some extra safety in that they can scan for it / pull the app without updating iOS, now you actually need an up-to-date OS.
It's a small additional risk but really not that big at all compared to what you can do with Android sideloading or app installing on macOS/Windows, and not comparable at all to macOS kernel extensions or Windows drivers.
I'm sorry but the way they interrupt the flow so many times is ridiculous. It would take minimal changes to make this flow non-disruptive but Apple wants users to drop off as much as possible during installation.
A lot of networked receivers/audio systems have C4A (Cast 4 Audio) built-in, and they should support grouping. I have a Sony receiver-esque audio system and it plays in sync with my Google Home speakers very nicely.
That is not the case. Only YouTube and Netflix have exceptions where the Android app on Google TV / Android TV intercepts the standard Chromecasting where the TV just pulls up the receiver web app in an ephemeral browser. And even for YouTube it'll automatically log you in in a temporary way when you cast. For anything else, casting to an Android TV device is exactly the same as casting to an old-school Chromecast.
I built a Chromecast receiver application for a broadcaster in Belgium back in 2017, and even then the original Chromecast was just a bit of a PITA. Our service was heavily ad supported, and porting our web ads to Chromecast was painful. The OG Chromecast was very hard to work on because of its super limited RAM. When connecting a remote Chrome debugger session you'd have to make sure to clear the console and network request history very often (multiple times per minute), otherwise the whole device would just crash. We generally only developed on the v2/Ultra and an Nvidia Shield, and then crossed our fingers to test on the OG Chromecast.
You can just call .isMock() on the location object you receive: https://developer.android.com/reference/android/location/Loc... - without root that can't be bypassed.