If you actually want to use your machine, keeping the machine from nuking itself shouldn’t be a hobby on its own. I need a reliable platform to work on, not a minefield on a fault line.
Don’t know what you’ve been using but I sure wouldn’t describe Arch as any of that. Once things are setup, I’ve extremely rarely run into issues that I didn’t cause myself.
“That I didn’t cause myself” is basically self-gaslighting. Using a system in exactly the way it’s supposed to be used shouldn’t cause any issues. Regular updates shouldn’t cause issues. Sure, it can happen, but it shouldn’t be the norm.
Recognizing your own mistakes is self-gaslighting now? FFS. And making a mistake sure is not “using a system in exactly the way it’s supposed to be used.”
Sometimes we make mistakes, it’s okay. If I wanted my OS to coddle me I wouldn’t be using Linux.
Again, this is exactly how the system is supposed to be used. You run whatever the update command is on your system occasionally. If that regularly breaks your system, the OS is not a stable platform. That might have its reasons, but it doesn’t change the facts.
It’s not a fact that updates regularly break the system. I’ve been using Arch for like 20 years now and I can count the amount of times that’s happened to me on one hand. I can do the same for CentOS and other distros as well.
It also wasn’t what I was referring to when I said I broke my shit by a mistake so you’re sticking words in my mouth.
Then you either have very large hands or don’t update that much. When I did use Arch for a while, Pacman often enough broke some stuff.
It also wasn’t what I was referring to when I said I broke my shit by a mistake so you’re sticking words in my mouth.
No, I interpret your words in a way appropriate here. You said, that only mistakes cause errors, I said that updates caused errors, and that I don’t think updates count as mistakes. So either you think that updating is a mistake, or we have fundamentally different experiences using Arch. I’m only sticking the shit in your mouth that you left their in the first place.
If you actually want to use your machine, keeping the machine from nuking itself shouldn’t be a hobby on its own. I need a reliable platform to work on, not a minefield on a fault line.
Don’t know what you’ve been using but I sure wouldn’t describe Arch as any of that. Once things are setup, I’ve extremely rarely run into issues that I didn’t cause myself.
“That I didn’t cause myself” is basically self-gaslighting. Using a system in exactly the way it’s supposed to be used shouldn’t cause any issues. Regular updates shouldn’t cause issues. Sure, it can happen, but it shouldn’t be the norm.
Recognizing your own mistakes is self-gaslighting now? FFS. And making a mistake sure is not “using a system in exactly the way it’s supposed to be used.”
Sometimes we make mistakes, it’s okay. If I wanted my OS to coddle me I wouldn’t be using Linux.
Doing an update is not a mistake.
Again, this is exactly how the system is supposed to be used. You run whatever the update command is on your system occasionally. If that regularly breaks your system, the OS is not a stable platform. That might have its reasons, but it doesn’t change the facts.
It’s not a fact that updates regularly break the system. I’ve been using Arch for like 20 years now and I can count the amount of times that’s happened to me on one hand. I can do the same for CentOS and other distros as well.
It also wasn’t what I was referring to when I said I broke my shit by a mistake so you’re sticking words in my mouth.
Then you either have very large hands or don’t update that much. When I did use Arch for a while, Pacman often enough broke some stuff.
No, I interpret your words in a way appropriate here. You said, that only mistakes cause errors, I said that updates caused errors, and that I don’t think updates count as mistakes. So either you think that updating is a mistake, or we have fundamentally different experiences using Arch. I’m only sticking the shit in your mouth that you left their in the first place.