Here's the original article instead of Yahoo blogspam:
https://apnews.com/article/dna-birth-switch-hospital-lawsuit-41e56f62fd6b8bb0afce8afc479ce7a8
Here's the original article instead of Yahoo blogspam:
https://apnews.com/article/dna-birth-switch-hospital-lawsuit-41e56f62fd6b8bb0afce8afc479ce7a8
Two minutes after I posted this, Doc 65 - Final Race Classification had been published: https://www.fia.com/system/files/decision-document/2026_belgian_grand_prix_-_final_race_classification.pdf
According to the commentators after they were looking into the rules said, an unsafe release during a race results in time or drive through penalty, not just a fine.
Man, if it was that simple, ALARM wouldn’t exist and arch would have (at least) allowed aarch64 packages in the AUR years ago.
Arch's policy is to offer only x64 binaries. They don't offer ARM packages because they don't want to. ALARM exists because Arch does not want the contributions.
While it's not zero work, your claim of reinventing the wheel overstates what compiling software that's already compatible with ARM requires.
I'm reading what Collabora wrote and nowhere is that blog post did they state that compiling stuff for ARM and the packaging are the hard parts. They explicitly called out the reproducibility parts, not the rest.
If your small community project with dead forums and broken logs (see below) can do it, a team of full time Linux engineers can do it in a relatively small amount of time, probably with logs.

Package repositories, recipes, and support paths
The existing stuff needs to be adapted, not reinvented. In my time as packaging some software for my own use under openSUSE I barely seen software that needed adaptions in the package spec file for other CPU architectures. Emulators were the most common exceptions I encountered and even that changed a lot since then thanks to upstreams porting those to Android and Apple M processors. Collabora lists as main challenges the ability to access the upstream source codes for reproducibility, not "repositories, recipes, and support paths".
Google is no longer supporting new Pixel phones in AOSP. The days of custom ROMs just working on Pixels is over. Consider getting Fairphone if custom ROMs are a must have for you.
It's a misleading headline. They aren't installing the app on your phone. They'll preinstall it on phones in the factory before they're sold.
What's there to reinvent? Upstream Linux software already builds for ARM.
It does put a small concern in the back of my mind for the Steam Frame
https://www.europe-consommateurs.eu/en/topics/guarantees/after-purchase/repair/
Sucks but luckily aftermarket batteries exists, so it's not the end of the world.

You don't need to be part of a real community to know this. Google Maps is good to check opening hours and how many reviews an establishment deleted, not for actually getting anywhere.