177
Can You Use Linux Without the Terminal? (How to Geek article)
(www.howtogeek.com)
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.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Yeah tbc once again I do actually use a GUI as well, I just think you're doing yourself a disservice if you refuse to even try using the terminal, because it's not as hard as you're telling yourself it is. For example, typing 'firefox' and hitting enter is way easier than looking for the icon and clicking it. When I was first starting out with it, I mainly worked by cycling through previous commands with the up key. Then you learn about Ctrl+R and you are flying.
Again, if you don't want to use the terminal that's up to you, and a perfectly reasonable preference. But don't make out that you couldn't learn it very quickly if you wanted to, because you definitely could!
I launch favourite commands with 2 clicks. Once on the App launcher button, and once on the App itself. My hand is on the mouse anyway. So it's fast. Way faster than typing a whole bunch of characters. For less used apps It's 3 clicks as I'd open a category like "Media" or "Games". And doing that, I get to see what I have in there. This builds up a picture in the users head for future use. Learning "Add to favourites" is time well spent. It can even be called "Pin to Start" or "Bookmark on Launcher" it doesn't matter. You don't need to memorise that exactly like the CLI. And right-clicking things is already second nature to huge numbers of users.
So I have no incentive to use text commands. It's not faster. My hand is on the mouse for my apps anyway. And the CLI has terrible usability, via poor learnability, zero tolerance, and poor visual feedback. And completely useless for most things I do, like working with 3D models, images or drawings. I'm not a "text-worker" like IT tend to be. Plus, I want more non-IT people to use Linux, so discovering the easy ways to do things can help spread the word to them.
For me it would be like stepping off a high-speed train and walking over uneven ground instead.
Ok but if we're talking about our own personal rigs, I launch favorite commands with one keystroke. I absolutely guarantee I can boot up my computer, navigate to whatever working directory and already have gotten to work before you've clicked on your second icon. But it's different use cases isn't it? I can definitely see how if you're using the mouse anyway, a GUI suits you better. I work mainly with text, but so do most people, I think? It's terms like "terrible usability" etc that I'm taking issue to here, because you're talking out of your arse. You admit that you've never bothered to learn, then make sweeping proclamations as if everyone on earth uses their computer primarily for Blender
Terrible usability will be the right term, if someone suggests applying one type of UI to an inappropriate situation/user/task. Such suggestions sadly seem to happen a lot in the Linux space. And saying CLI is easier is a sweeping proclamation. Whereas I've avoided making sweeping proclamations, repeatedly describing the many cases where CLI is poor. Usability analysis needs to know about the user and the situation. It's not one size fits all.
I've used various command line systems a lot in the past.
I'm saying it's more productive for many to invest in extending learning their home environment than learning a completely unfamiliar and inappropriate environment.
Your criticisms are literally general ones. You've only gone into specifics to describe the configuration of your favorites bar in detail for some reason. I've been saying throughout this conversation that it's a question of use case — that making general statements about 'usability' overlook a whole host of users; the visually impaired being one example that comes immediately to mind. The point is that there should be options, and people shouldn't be put off from trying different things until they find what works for them, because for everyone who needs a GUI-only approach, there is someone else who would benefit from a bit of CLI in their workflow but has been told it's beyond them when it really isn't.