Yeh, unsure about that, given that Windows has 90% of the desktop OS market, but is a steaming pile…
Anyhow, the Arch news tends to be soporific, so I like to live dangerously, and update a couple of times per day from Testing.
You can usually get a feel for what might have minor issues and what might cause your system to be unbootable or unusable.
I never run an update if I don’t have at least some time to kill to troubleshoot anything that might come up.
If there’s a critical package update waiting like a gnome-shell update, or new linux kernel, new nvidia drivers, systemd, Xorg/wayland update, I usually hold off on hitting that button and do a quick check of these forums/reddit (both in the /r/endeavouros area and /r/archlinux), usually if there’s something buggy with those, there’s people already chatting about it.
I run btrfs with timeshift so the pacman hook auto-snapshots my system before each update. It takes some of the bite out of it knowing that, generally, if something gets screwed up you can reload the snapshot back to the last known-good config until you have time to work through the issue.
Just be smart about it, have some common sense and it’s not so scary.
EDIT: Man, blanked on Timeshift’s name and went back to my old OS X days…
It has been so long since it happened - but I seem to recall the eos-notifier, unless configured NOT to do so, will inform you of the existence of Arch news is there is anything actually ‘new’. A real time saver when relevant! OF course, any number of the strategies discussed here also work.
I am a bit of a woose and run the LTS kernel. My laptop that I have Endeavour on is so old that the LTS kernel is overkill cutting edge!
Yep, same here. On my main computer, I run it so It doesn’t go down.
On this Laptop with Endeavour, I have it because I want to use it as my ‘play’ computer. One that I can experiment and try things out - that always leads to problems for me, so TimeShift is my friend as are auto-snapshots.