this post was submitted on 18 Aug 2025
652 points (98.2% liked)

Technology

74319 readers
4489 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] gian@lemmy.grys.it 1 points 1 day ago

I used Arch for about 7 years. I still have it installed on an old PC but I haven’t used it recently. Every time I told pacman to update everything it felt like an adventure. Never knew if I was going to reboot to a working desktop or to a console printing cryptic error messages that take a while to Google on my phone before I get things back up and running. I wouldn’t wish that experience on my worst enemy’s grandma!

The only times I got this kind of problems where when I didn't read some announcement or for some reason some packages (the kernel) were way too old, normally never had it on a normal update. But as I said, you have a point, even if in the end I would point out that a grandma would never be able to solve any problem caused by an update, irregardless of the distro or the OS.

It all comes down to the maintainers of Arch putting all of the responsibility for breakage (especially due to old configuration files) 100% on the user. That’s not a system any normal person should use, that’s a system for Linux hobbyists.

Only partially. Normally Arch put the new configuration file as a [something].pacnew and it is the user that should then do something, but as long as the software that use the new file could undertand that it is using an older file and it is able to handle the eventually missing new keys or removed ones there will be no problem. On my desktop I have a bunch of [some_program].conf.pacnew and everything works. Is it optimal ? Maybe not but it is not broke.

It’s fine if you want to assume all responsibility for updating grandma’s system and fixing breakage every time. I don’t have any interest in doing that.

Honestly, a grandma would just need Firefox with a couple of extension (uBlock Origin and really few others) and a network with all inbound ports blocked (so no one can connect from outside) and few outbound ports open (very few, just the common ones to use a browser). Maybe she need Openoffice, probably a DE (but a window manager could be enough) but she don't need a lot of software we all install on out machine. It is true that Arch could be a problem when updating but I think we are talking of a very small set of packages that need to be constantly updated and in my years of Arch usage, basic packages rarely break something while updating.