That would break history in all SPAs.

Snap is Canonical’s project AFAIK

A well-made online gambling “game” is harmful

If you choose to run linux-lts, sure, but the plain linux package also exists and is at 6.19.9.

He probably means Ubiquiti network gear

Yes, but it is a binary blob that Google makes and Firefox just integrates with. If it is not released for a specific platform, Firefox can’t do anything about it. At least a while a go it was quite an adventure to try and get DRM working on ARM64 Linux: https://www.da.vidbuchanan.co.uk/blog/netflix-on-asahi.html

This is good even if you don’t care about Chrome, because it means Widevine should become properly supported on the platform.

I don’t get Google’s “iOS, but worse” strategy, I’ll just buy a fucking iPhone then.

Oh yeah, installing Steam from a flatpak also seems to be a good way to avoid some tinkering, I don’t think they have ever done that.

They don’t need to stop, GrapheneOS will just be an officially supported alternative OS. Their own Android flavour can still be as full of crap as ever.

Like hard reset required “bricked” or dumpster bricked?

It’s less about the chips and more about what extra components have they snuck onto the motherboard. Supermicro supposedly had this happen: https://www.bloomberg.com/features/2021-supermicro/

Right, but Apple is doing this because most users have switched to ARM at this point and they will be ending software support for x86. So it seems safe to presume Intel macs will become cheap.

Android TV also had similar issues

I wouldn’t expect it to matter much, idle processes are pretty cheap.

Great, now read it row by row without keeping it all in memory.

Compression adds another layer of complexity for parsing.

JSON can also have configuration mismatch problems. Main one that comes to mind is case (in)sensitivity for keys.

CSV >>> JSON when dealing with large tabular data:

1. Can be parsed row by row
2. Does not repeat column names, more complicated (so slower) to parse

1 can be solved with JSONL, but 2 is unavoidable.

…in a virtual machine

And even if something is not on the AUR, I could see myself writing a PKGBUILD for it, unlike most other packaging formats.