When they had us stand up in grade school and pledge allegiance to the flag. Nope, no thanks. If we're that amazing we wouldn't compel children to worship nationalist symbols, we'd give them reasons to be proud of their country rather than trying to compel worship.
On the other hand we're #1 at a lot of things, like medical bankruptcies, mass shootings and incarceration per capita. So, go us and our amazing country?
Btrfs, ZFS and ext4. My servers use ZFS, my client machines mostly use btrfs and I have a sprinkling of ext4 partitions for specific workloads. I'm all in on CoW filesystems for snapshots, send receive, transparent compression and reflinks. I like btrfs on client machines and SBCs because it's easily available (baked into the kernel) and doesn't require maintaining dkms or holding kernel versions until ZFS supports them and because snapshot handling and other filesystem admin tasks are simple and straightforward. I run ZFS wherever data integrity is important, eg: storage servers and backup targets, but largely prefer working with btrfs.
Zelle is sketchy even when compared to other cash transfer apps. They do a lot of freezing people's money. Don't use them if you have any other option.
I mean, it seems like his politics are exactly where they should be w.r.t. Beijing.
The whole Republican take that "anyone left of Reagan is a raging communist" has been flogged so hard that there's not even a horse carcass left to beat anymore. We just expect them to say that about anyone not on a GOP ticket and, honestly, we should be more worried when they don't trot that line out.
Flatpak is a great choice for Steam in particular. The native install requires a full 32bit multilib stack from your distros package repo, flatpak steam boxes all of that up on its own.
I try to use flatpak for GUI apps where possible, those don't need unrestricted access to my user data in most cases.
Flatpak is slowly improving. I think the biggest problem with the flatpak ecosystem is lack of widespread understanding by new maintainers of how to package flatpak well - you see a lot of new packages by software authors who don't yet understand flatpak permissions and package quality suffers for it.
There are some annoyances, like some of the XDG portals being jank, but it's a solid step towards containerizing and jailing individual apps so they can't access more of your system than they need to do their job.
Flatpak steam, as an example, is fantastic. You install it, maybe drop in a proton version that works better for your game and you're ready to go. Same deal with many desktop applications, flatpak discord and others work extremely well and, at least compared to the Arch native versions, don't break as often.
Edit: Chiming in on Fedora and EndeavourOS, they're both excellent choices and not much more difficult to use than Ubuntu.
I don't encourage people to buy anything older than ~2016 or Skylake era. Older chips tend to eat enough power that they're more expensive over time (usually less than a year after purchase) than newer more power efficient parts. Run the math on power consumption with the chip's TDP for a year as an estimate and you'll often be surprised by just how expensive chips from <2016 end up being to run. Cpubenchmark.net will do that for you if you use the comparator, just remember to set your average kWh cost.
So many of those people treat their cat like a lamp though. Of course your cat is a "loner sociopath" - if you barely interact with it and never give it attention or enrichment it's going to fuck off and do its own thing without you.
Optimized jpegxl decoding can be as fast as jpeg but only if the browser supports the format natively. If you're trying to bolt jxl decoding onto a legacy browser your options become JavaScript and WASM decoding. WASM can be as fast but browsers released before like 2020 won't support it and need to use JavaScript to do the job. Decoding jxl in JavaScript is, let's just say it's not fast and it's not guaranteed to work on legacy browsers and older machines. Additionally any of these bolt on mechanisms require sending the decoder package on page load so unless you're able to load that from the user's cache you pay the bandwidth/time price of downloading and initializing the decoder code before images even start to render on the page. Ultimately bolting on support for the new format just isn't worth the cost of the implementation in many cases so sites usually implement fallback to the older format as well.
Webp succeeded because Google rammed the format through and they did that because they controlled the standard. You'll see the same thing happen with the jpegli format next, it lifts the majority of its featureset from jpegxl and Google controls the standard.
When they had us stand up in grade school and pledge allegiance to the flag. Nope, no thanks. If we're that amazing we wouldn't compel children to worship nationalist symbols, we'd give them reasons to be proud of their country rather than trying to compel worship.
On the other hand we're #1 at a lot of things, like medical bankruptcies, mass shootings and incarceration per capita. So, go us and our amazing country?