|
|
|
|
|
by hiram112
1748 days ago
|
|
> Do you Linux users just apply random advice like that off the internets without seeing what every line means? This isn't just a Linux issue. I've used Windows many years, and the vast majority of solutions to problems is inserting some cryptic string into the registry and rebooting. Though I eventually dumped Linux, too, a few years ago as the solutions to the weekly show-stopping bugs, driver issues, and kernel glitches constantly required the same type of unintelligible shell commands copied and pasted from some random blog. Unlike earlier days of Linux, the commands now were completely foreign to even long-time users of Linux who understood most of the main components of a standard Linux install. It would require modifying some file in /etc or using some sub-component or binary that I'd never ever heard of and had no idea why it was even included into my "base" install of Fedora or Redhat or whatever distro was downstream. I blame mostly RedHat for this change; Systemd may not have always been the problem, but its design and complexity (compared to traditional minimal Unix "do one thing and do it well") is a good metaphor for how modern Linux has been bastardized into just another black-box like Windows, where your only solution for many problems is some esoteric command which must be pasted off of some RHEL paid-license-required mailing list. |
|
But the issue I have is that it's very difficult to mess up your computer as a Windows/Mac beginner, but you have to play with fire pretty frequently as a Linux beginner.