3 ms·
> Linux is way way way less likely to just change something and break the whole system while the user is sleeping I take it you have never had to try and corre
by neilalexander 6y ago
> Linux is way way way less likely to just change something and break the whole system while the user is sleeping
I take it you have never had to try and correct a system broken by seemingly innocent-looking aptitude or RPM package upgrades. :-)
> Fixing a Windows problem can involve having to go into the registry, which can't be copy/pasted and is extremely difficult AND dangerous. (There probably IS a way to copy/paste it, but I don't know it).
I’m really not sure the registry is any more “dangerous”. For many everyday users, I would guess that the perceived complexity of the registry and of configuration files scattered throughout the system are really about the same. Both can appear cryptic and fragile.
On the one hand, you might accidentally delete something important in the registry. On the other hand, you might forget a quotemark/character or get some indentation wrong in a configuration file and be surprised when the entire thing breaks.
- larrik 6y ago> I take it you have never had to try and correct a system broken by seemingly innocent-looking aptitude or RPM package upgrades. :-) Keep in mind that on Win10 you don't even have to click a button, and the updates aren't even avoidable. > I’m really not sure the registry is any more “dangerous”. For many everyday users, I would guess that the perceived complexity of the registry and of configuration files scattered throughout the system are really about the same. Both can appear cryptic and fragile. I dunno, once they are in the registry, it's like putting every config file on the whole system into their home/documents directory...
- Koshkin 6y ago> broken by seemingly innocent-looking aptitude or RPM package upgrades Not on Slackware, no.