Being able to do this is why Linux is so amazing. If Windows finds a corrupt file and can't repair itself, you gotta find the package it's part of (Windows update catalog), or create an ISO that's updated to do an offline repair. If the registry gets fucked, good luck fixing that.
Arch is not meant to be a daily driver if you're expecting "shit just works" stability long term when you just blindly run updates. You have to understand what you're updating and sometimes why.
It is targeted at the proficient GNU/Linux user, or anyone with a do-it-yourself attitude who is willing to read the documentation, and solve their own problems.
If you want to use Arch, you need to invest in snapshots using rsync or dd. Given how it's a rolling release, you should do this weekly. If something fucks up, grab all your logs and put them somewhere safe. Roll back and look at your logs to see what broke. Then apply updates as needed. You can ignore packages for quite a while. If you're not smart enough to understand it now, you may in the future. It takes time and practice.
Debian based is only "out of date" feature wise because they do a package freeze. They ensure stability before release. Updates are largely security related.
I somehow broke my Debian bookworm install… ( lemmy.world )
It’s not really broken, couldn’t get the microphone to work with any program
The fix is scheduled for the next release ( lemmy.blahaj.zone )
Image text: "Fact: 90% of Linux users switch back to windows right before all their problems are about to be fixed"