Yeah, that’s a very common misconception, that you constantly have to “maintain” Arch, as if something happens to it just by having your computer running.

I do very little “maintenance” other than issue these commands:

$ paru
...
$ flatpak update
...

Before I upgrade the system, I check archlinux.org in order to see if there are any breaking changes that need manual handling. (Has happened maybe 2 times with packages that I have actually had installed, in 10+ years.)

Then, when paru has invoked pacman and upgraded native packages (from the Arch repo) and starts to upgrade foreign packages (from the AUR), I check the diffs in the package files (paru displays them) to make sure nothing looks fishy. Obviously upgrading Flatpak packages needs no maintenance.

This all takes about 5 minutes each time I do it, including downloading of new package versions, which is very little time per week. Even less if you do it less frequently, which you definitely can.

So when you say I do a good job maintaining Arch, is not really me. 😅 The Arch developers have done a superb job for me. And the maintainers of the Arch wiki are also true heroes. I just use it. 👍

The page you linked to is slightly FUD and yet simultaneously true because theoretically anything can happen and that serves as a disclaimer that the developers shouldn’t be to blame, and nobody is owed support if something were to potentially break.

Ubuntu broke loads of times for me back in the day. Had to reinstall it several times. And all I did was issue the command for upgrading to a new Ubuntu point release. 😅