this post was submitted on 19 May 2024
160 points (90.8% liked)
Linux
48371 readers
1743 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think not everyone needs to know how their device works. Specialization is what advances us as humans after all. If they wanted to know, good for them, and if they don't also good for them. If I were using a car, I don't need to know how the engine convert a chemical energy, transfer power, and generate thrust
Edit just to give an example, an office worker may only need to use a word processor and their OS be up to date. If the user can just click the GUI to update the OS rather than typing the command for whatever package manager the OS uses, it is good enough for him. Sysadmin can give them the instruction once and done.
If the user forgot the instruction, they can explore it on their own with GUI without internet since no matter how deep a GUI config is, then there must be a way to get there (assuming the UI designer isn't shit). Contrast that with CLI where if you forgot or don't know any command there is little help or indicator of what's available and what can be done without external help.
I could not agree more. The number of people in here who are demanding that everyone who uses an OS understand it completely is absolutely ridiculous. I’d love to sit down and watch these people rebuild a lawnmower engine or service the compressor on their refrigerator. Hell, a shocking number of people I meet don’t know how to cook for themselves and they’re going to demand that end users be able to chroot and save a nonbootable system? Get out of here.
It's pretty unreasonable to expect people to know all the intricacies of their OS unless it's their job, but I do think people could stand to treat their computer less like an unknowable magic box when they need to work with it and take a few minutes to try any basic troubleshooting at all. An example of the sort of thing I'm talking about, last year, my fan stopped working nearly as well and began making crazy amounts of noise. Could I explain to you how the motor in my fan works? Absolutely not. But I unplugged it, looked up how to disassemble it and got out my screwdrivers and opened it up to see if there was anything that I could see wrong with it. Turns out there was a lot of hair wrapped around a shaft and the base of the blades that built up over the years I've had it, and removing that and reassembling it was all it took to get it working fine again.
Plenty of people don't want to put in even that small amount of time and effort to understand things when it comes to computers, which is also a valid choice of its own, but they tend to annoy me when they attribute being unable to do something to the system being too complicated to understand/use, rather than owning their decision to focus their time and energy elsewhere. There are absolutely complex programs that are not accessible for non-tech people on Linux or the BSDs, but the same could be said for Windows and Mac. In the case of the other two, people just choose the option that works for them, but with Linux, they decide ahead of time that Linux is tough and complicated and don't even try. It could be something as simple as they want to install Debian and need non-free firmware to use their wireless card, there are people who will declare this to complicated to understand and discard the idea of using an OS entirely over a question that can be resolved in less than 5 minutes with a quick search and nano, all because "Oh, I'm not a computer person, it says terminal."
Yeah, you do make a good point about misattributing the system being incapable to their lack of research. But people don't like it when they are wrong/corrected most of the time. It also applies everywhere, computers just so happen to be the most prominent. The point is that people will complain about anything anywhere.
You bring up an example of installing Debian and needing non-free firmware for their wireless card. Take a step back and think how many people are even aware about the term non-free? It is quite a ubiquitous english word with different meanings in the open source community. People reading it will assume they know what it means.
The scenario when someone that is fed up with windows and decides to install debian will see the word "non-free" and attribute it to "you must pay" at glance. If the resource they used to install it mentions and clarify what non-free means, good. Otherwise, it can be a boogeyman for them and make them re-think their decision to switch.
Ikr? "Since it interest me, it you interest you too"
manwould like to have words with your strawman.And how does the user suppose to know to type
man? He may remember the instructions to check man, but he may not. For us, those 3 letter words are very familiar, but others need time to remember them. On GUI, this is no problem because as I stated they will bound to find it by exploring. Basically point and click adventure games I guess rather than the guessing game. And users will choose the path they most familiar first.Bigger problem, even if they know about MAN pages, remembering what their looking for is hard. You can't type 'man dnf' if you don't remember what your package manager is called.
I wonder how feasible searching MAN pages is.
Yeah good point. Navigation can be unintuitive too. Like, how do you quit? Is it q? Ctrl+C? What even is the weird symbol before C? Those are some of the hurdles that must be overcome when coming to CLI and not necessarily easy to remember. Sure you can do it in 1 hour, but say tomorrow would you remember it again? What if the system is running smoothly for 1 month and you never opened the terminal again after those 1 hour?
You don't need man, just type the command with no arguments and you'll get the help message.
Alright, try it with
cat