No wrong times, only small periods of unfortunate times!

I think you mean there’s never a right time to update! You’re always rolling the dice!

A wrecked bootloader is not a problem, but a lesson to keep a usb drive to be able to chroot.

Atomic distro users: Look what they need to mimic a fraction of our power!

That's Harry Potter

Spoiler alert Snape kills Boromir

The moment I finally installed Arch was then I felt "freedom" for the first time. No longer do I need to make compromises on my system and have things installed that I don't need or want. It's my system that I put together the way I like it. A bonus is that I know my system pretty well if something should break and I have the wiki to guide me

Should've installed Intel.

I had this happen once or twice, caused by bad Nvidia drivers with Wayland.

I use AMD now for my day job, haven't had a single issue in over two years. That's not to say you should use it - it's still a rolling release distro and will always have a potential to break over most other distros.

Ubuntu has never been remotely stable for me. Something stupid breaks or becomes difficult to get what I want out of it.

Been that way since it came out for me.

I find Arch much less hassle than Ubuntu ever was.

Just recently put Ubuntu on a machine for a work project. It was broken from the get go, throwing errors and being it's usual shitty self.

I could never recommend it.

Fedora on the other hand has been on a spare laptop for about 6 months and I gotta say they really have put some polish in. Updates are frequent but reasonable and most everything works well. Some small issues but they are not show stoppers and Fedora is aware of them.

And I like having my software up-to-date. It sucked ass when I was on Mint and one of my favorite programs had an update and I had to wait months for it to hit the repos.

I've been thinking about Debian and Ultramarine Linux (fedora but with drivers and less setup)

a bash script to reinstall f—ing everything again

Why would you ever want to do that?

First of all, almost any Arch update induced problem can be solved by downgrading the offending package to the previous version, which handily is available in /var/cache/pacman/pkg/. This is an essential Arch troubleshooting skill.

Even an unbootable system (which has only happened once in my 10 years of using Arch because I didn't read important news) can be fixed this way, because you can always boot from the installation usb stick and then use arch-chroot to access your installation and fix problems.

Secondly, if the problem was indeed caused by an Arch update, you will just reinstall the problem if you run a reinstall script.

You reinvented NixOS

It's not the kernel but always mkinit in my case, on multiple machines. Even if i did never do nothing related. And booster/dracut and Efistub somehow never worked.

Just don't try plugging it into a Raspberry Pi 5.

No data loss, but won't work without changing your kernel. The other way around is much worse though

you can use an RPi5 to make a BTRFS drive which essentially only works on RPi5s.

Why would you need to do that? Just use something stable.

Sure it is, but we are lazy you know.

I don't have time for my system to be borked every 2 years. That's why I use Arch.

I have been using Arch and EOS a lot longer with no borks.

Been using EOS a lot longer and always flawless.

The only problem I have had is leaving a system too long and having to remember how to get the damn keyring to refresh. That is my biggest complaint.