Maybe so, but it’s much harder to learn from your mistakes and fix them on distros like Ubuntu.
I say this as someone who has recently switched to Arch because my Windows existence was aggravating me and I had never clicked well with Linux in the past. It felt too unfamiliar and I think I’m the kind of masochistic weirdo who benefits from their first proper go at Linux being Arch.
I still don’t have a fully working setup on my desktop yet because I’m working on doing it properly, but problems and mistakes are much easier to fix on Arch than on any other distro I’ve used.
Lol, that’s fair. If I would have spent significant hours researching all the changes and the new config files, I probably could have had a better time.
However, around that time I decided that dist-upgrades were: 1) for the birds, and 2) like Windows in that it’s easier & better to wipe and reinstall.
It’s how I was in my first few years of Linux too. I think I started reading to understand what’s happening around Ubuntu 10.04. These days nothing scares me. I had a power failure during a 20.04 -> 22.04 upgrade. Shrugged, finished the upgrade procedure manually once the power came on. That particular machine hasn’t been nuked and paved since 14.04 or 16.04. Once you’re confident in what the system does, e.g. what apt and dpkg do, you can use them to do a lot. E.g. you can use dpkg to verify that all installed files for all packages exist and are indeed uncorrupted. Or compare a modified config file to the package one. And so on. I literally did a system file integrity check with dpkg on my corpo workstation the other day, after its SSD decided to disconnect from the system while it was running.
The Ubuntu failure was likely also your fault. 😄
Maybe so, but it’s much harder to learn from your mistakes and fix them on distros like Ubuntu.
I say this as someone who has recently switched to Arch because my Windows existence was aggravating me and I had never clicked well with Linux in the past. It felt too unfamiliar and I think I’m the kind of masochistic weirdo who benefits from their first proper go at Linux being Arch.
I still don’t have a fully working setup on my desktop yet because I’m working on doing it properly, but problems and mistakes are much easier to fix on Arch than on any other distro I’ve used.
Lol, that’s fair. If I would have spent significant hours researching all the changes and the new config files, I probably could have had a better time.
However, around that time I decided that dist-upgrades were: 1) for the birds, and 2) like Windows in that it’s easier & better to wipe and reinstall.
It’s how I was in my first few years of Linux too. I think I started reading to understand what’s happening around Ubuntu 10.04. These days nothing scares me. I had a power failure during a 20.04 -> 22.04 upgrade. Shrugged, finished the upgrade procedure manually once the power came on. That particular machine hasn’t been nuked and paved since 14.04 or 16.04. Once you’re confident in what the system does, e.g. what apt and dpkg do, you can use them to do a lot. E.g. you can use dpkg to verify that all installed files for all packages exist and are indeed uncorrupted. Or compare a modified config file to the package one. And so on. I literally did a system file integrity check with dpkg on my corpo workstation the other day, after its SSD decided to disconnect from the system while it was running.
Standard Linux incel user blaming.
It’s true. Ever since I got married, intercourse has been at a premium.