Then again, I haven't used Arch in such a manner, so you might as well be right.
sudo pacman -Sy archlinux-keyring && sudo pacman -Syu
There were two times something went wrong:- when Arch moved plymouth to their main repos
- when switching from a 1070 to a 4070 I needed to recompile my nvidia drivers
The other one seemed to have been updated last time in 2015. It didn't even have updated certificates for https, so it couldn't sync the keyring. After trying for a while I just gave up and reinstalled Arch from a USB stick.
> not updated since 2021
That being said, for day to day stuff Arch (and Nix standalone) works well enough for me, to be weary of switching my daily driver PC to Nix, out of the fear of dealing with unforeseen issues and maybe encountering less well maintained packages (there's always something broken on Nix unstable, but maybe it's not an issue for more popular stuff). So I'm sticking to Arch for non-servers for now.
Here we talk about a tiny percent of the tiny 3% of desktop users.
If you're going to be snide, you should at least be correct - or are the 6300 users in the main matrix chat room just hanging out for fun?
(sent from my nixos daily driver)
Hell, even in a Linux-only context too. I mean, an exchange like:
- We're shipping this enterprise software in packages compatible with RHEL and Ubuntu, would it be worth our while to also devote resources to specifically support Arch too?
- Nah, nobody uses Arch
While not accurate to the maximum possible precision (something like say 5% of Linux users is not the same as 0%), it would still be quite understandable...
The irony. You’re aware Arch its policy is to release packages in a broken state and just put it in the release log? They even very publicly state that.
If you want an actually stable rolling release, stick with OpenSUSE.
Can you please provide some sources/examples?