I think they meant that rendering can only be done with JS/HTML, and if you want to use React stuff, React also has to be involved. No need to be rude and assume the worst.
Third point seems true though, I would definitely expect to see JS errors should any React libs have issues on their own.
Because users get a scary warning if they don't do that. Unlike Mac or Windows, where users can download stuff outside the Mac or MS store without warning, so big companies don't use the stores.
Apple Silicon Macs. Aside from that, yes very boring, especially the silly stuff like watches, pencils, and credit cards. That said, I'd rather our country respect private property, also it's not like there's a ton more innovation left in these spaces anyway.
Android heavily warns users against installing those, which might not fly if the ruling is to treat them equally. Despite that, a major app Fortnite is only available via the Epic Games store on Android.
My Apple BT keyboards+mice run out of battery very quickly and sometimes randomly disconnect/reconnect. A newer non-Apple BT keyboard seems ok on its own, but then there are issues on the other end. My fairly new Windows PC can't wake up from Bluetooth keyboards/mice, so I have to keep a USB one attached. And the BIOS menu requires a USB keyboard too. Dongle eliminates all that complexity.
There are also some BT limitations at play. Key rollover is capped, and mouse polling rate is lower. But that'd only matter to me if I were playing PC games. Ability to switch devices is a plus for BT.
I tried my Bose NC700 with my Pixel 6. It gave me the quick-pairing notification, asking me also to install an app, which ofc I said no to. Then when it was already paired, I got the pairing notification 6 more times during my call.
Probably doesn't happen for everyone, otherwise it'd be fixed. But that's how it always is with overly complicated stuff, edge cases everywhere.
Yes. I scrolled and found it by chance: "Simply put, your brain is trying to figure out what it’s hearing, so it’s filling in the gaps of the noise you’re listening to with a common sound."
Cmd+f found no mention of AM radio in there, which is another possible explanation for hearing voices or music in those machines. If I were hearing that, I wouldn't appreciate this article telling me it's in my head.
1. Allowing other app stores would immediately mean each app wanting you to go to a separate store. I barely use apps in the first place but would imagine this being bothersome for those who use them a lot.
2. I don't want my phone to run arbitrary code, that's what my Mac is for. People install unknown third-party apps on their iPhones all the time, which is safe enough. Now imagine Apple was forced to make iPhones more like Macs in this respect. When was the last time you installed an unknown third-party Mac app?
3. If the govt does something along the lines of preventing Apple from pre-installing their own apps, or some other way of forcibly informing users that they have alternatives, that's annoying for anyone who uses those default apps anyway.
4. Forcibly opening the iMessage protocol could lead to more spam or hold up Apple adding new features that Android doesn't support. And Apple is going to adopt RCS anyway.
5. Govt regulations on software have historically not done much good for regular users. GDPR got us modal cookie notifications on every site, which some nerds really liked along with the takeout stuff, but most people saw as useless and annoying. Plenty of iPhone users are happy with the status quo.
I'm fine with this. Apple can extend sucky BT, Apple can make their faster Apple Silicon chips, Apple can make iMessage since SMS is trash, Nvidia can do CUDA cause OpenCL sucked, whatever. Just don't also intentionally kneecap the competitors by removing their interfaces.
Yeah, try setting your nav from Los Angeles to Irvine or San Diego to Irvine on any given day. Guaranteed 2-3 wrecks, plus some jams that the nav might think are wrecks but are just phantom jams.
Also, many newer cars will automatically downshift if they think you want to engine-brake. Usually based on the fact that your foot is off the gas and on the brake for a long period of time.
Third point seems true though, I would definitely expect to see JS errors should any React libs have issues on their own.