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
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.
What? Do you understand what I'm asking? Do you understand what you're suggesting?
So googling how to do someone, copy/pasting command is better than finding it in GUI? How high are you?
Again a solved problem, just make a decent GUI for your application.
Ok, I'll try again:
You are promoting monolithic design. You completely fail to comprehend Unix philosophy:
GUIs are only used for human/application interaction. They are not needed for application/application interaction. While it is not unreasonable to have a GUI for interactive input within your application, it is infeasible and undesirable for a GUI to be needed for your application to interoperate with other applications.
Go ahead and create the GUI if you really want, but expect your users to want to call it from a shell script. Give users the capability to automate away unnecessary manual interaction, and allow the machine to take up that pointless busywork.
Oh, absolutely. Especially for a one-off setting that you might never look for again. There's just no sense in wasting the time building up a complex GUI to handle every possible interaction a user could ever want to employ.
The solution to the "problem" of "needing to use the terminal" is to retrain the user to understand how limiting even the best GUI can be, and to greatly prefer the terminal.
So, my suggestion is, rather than try to hide away the terminal, it should be featured prominently, exposing the limitations and shortage of command line applications available to windows users.