Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
An effective terminal is a feature, not a bug. Every Linux problem has the same solution: search the web, ctrl-c, ctrl-v.
No navigating through "settings" and "preferences" and "tools" menus to figure out where this particular developer decided to hide that particular setting. Just copy and paste, problem solved.
That's a bad take. Learning the bad habit of copy/pasting command and depending on the Internet to do the most basic changes to your computer is not a "feature" of the terminal. I can Google how to navigate Windows control center too.
Setting search is a solved problem, you simply search for the setting name in the UI, it's way easier than navigating terminal flags and switches.
This assumes the developer bothered to make that setting available through the UI.
With the terminal, that isn't a problem: You're using the same UI as the developer.
That assumes the programmer bothered to make user friendly flags... The terminal doesn't magically just work.
With open source, the delineation between "user" and "programmer" is arbitrary and capricious. The GUI-centric Windows approach reinforces that artificial distinction; the terminal breaches that barrier.
Are you suggesting users with no programming experience can simply add the flags they need to a terminal application but would be unable to do the same with a GUI because the GUI is the barrier? Not the logic and that the program will do with the flag, but the GUI is the barrier?
What are you saying?
Yeah, why not? I'll go ahead and make that suggestion.
I mean, the terminal allows them to ctrl-c, ctrl-v a simple solution developed by someone else, even if that someone else didn't bother to build out a GUI for applying their changes.
The convoluted steps they would have to take to achieve the same effect with a GUI would seriously hinder the GUI-only user.
What I am really saying, though, is that the problem of "needing to use the terminal" is not actually solved by ensuring that every possible setting can be accessed and manipulated with a mouse.
I'm saying that the best way to solve this "problem" is by pushing the user to expect and even demand the terminal. Distros should autolaunch a terminal window at startup. Put it right out there, front and center. Invite the novice user to interact with it with friendly little toys like fortune, cowsay, sl, toilet, espeak. The insane usefulness of the various shell tools are more than enough to keep them using it.