The Registry Editor is a GUI that doesn’t rely on memorising commands. This is home territory for users. A tree to navigate, similar to a file manager is very familiar. Even the first time. Just give me the path. It is also easy to work out how to edit entries, and to revert changes. Sure, you might not like the looks of it. But it lies in the ‘normal’ world. Not in some strange world. People not into usability sometimes don’t get that.
Yes. I’ve been using Linux for over 10 years without touching the command line. I used Ubuntu up to Unity, then switched to Kubuntu and Plasma. I’m not in IT, so I don’t need IT stuff. It all works by GUI. People who haven’t tried it might say it’s not possible. But they are not speaking from experience. Some others, not interested usability, don’t understand why GUIs are so successful and dominant. Which is absolutely fine, as long as they don’t try think they are suddenly knowledgeable in usability, and have tried 10+ years of GUI only.
The CLI has lots of hurdles. Such having a blank screen with no prompts. Where the GUI shows the options you have. And 1 click to set the option. And how to unset the option is obvious. You only need to half remember a feature. Not precisely memorise and type command exactly or it will fail. Or worse, delete something you need. The GUI is preferred by the vast majority for good reason.
The CLI is not faster for everyone. Especially non IT users who don’t know any of the options and would have to search the web every time. And there are so many commands the CLI is useless at. Graphics and presentations a big fail. And few people use CLI for email or spreadsheets.
GUI users have a chance to work out how to use a new GUI 99% of the time, as it is all familiar. No exact syntax to type perfectly or it will fail. On other occasions, web help tells you where an option or command is. There is no need to entirety change the way you work, just for a few times when learning new software.
I use the Plasma app store Discover to update, upgrade, install and uninstall apps. Everything is easy. Even unpacking files and permissions are easy in the file manager. No need for CLI as I’m a home PC user.
Yes. You can bork your system via the registry. But only some parts of the registry are dangerous. Changing the mouse scrolling direction as I do, hasn’t given me issues so far.
Sure there are some people who can’t do anything. But there are a large number of full time computer users not in IT who know their GUIs really well. These are candidates to switch to Linux.
If you give someone a text string to paste in, chances are they won’t be able to tell if it worked. They might need another command for that. And how can they undo that command? And the next time they need that command they’ll have to have stored that command string somewhere! Which is why it is better to show them the option in their application GUI, as the GUI will provide feedback on the status. And makes it obvious how to undo the change, and they know where to go next time. Otherwise they are dependent on you forever. Also, I doubt if there are any text commands for most things I do on a computer.
You don’t design a UI around the relatively few occasions when GUI help is too hard for some helper.
It’s not always *fear *of the CLI. I am not interested in memorising a whole load of unnecessary stuff I’d need, to start using a CLI, that I can already do productively with the GUIs. I’m not in IT. I know my way around GUI applications quite well. So it’s more worthwhile extending my knowledge there.
If a user speaks a different language, good usability knowledge will tell you, change the software to help the user. Not change the user to help the software. The software is only there to make things easier for people.
As I said for many people, the tasks they do are not always possible or not easy with the CLI. Try drawing a curve, try moving an object from bottom left to a position higher up to the right. Even navigating a tree structure, common in many apps, it’s easy to click on a chosen branch directly. Even with CLI options, more people, including CLI users, feel it’s natural to use a GUI app to do their email, manage files or browse the web. There is a lot of learnability built in. Discovering new things by accident is a natural benefit. And a big downside of the CLI. Which is not THE natural way at all.
Yes. I’ve been using Ubuntu and now Kubuntu for about 12 years and I don’t use the CLI. I don’t play computer maintenance guy, so don’t need any weird hacks. I just use my applications, which all have GUIs. I don’t need the CLI despite people telling me I need to use it. They have never tried GUI only. So they don’t know what they are talking about. The next lot, who typically have no idea about usability, tell me I’m missing out on something. But it’s always something I’ve never needed. If I were to use the CLI, I would need to spend ages researching not just some command, but a whole lot of other concepts that I have no clue about, only to forget it all if I ever need that again. So not as fast as people claim. Luckily, Desktop Environment developers know this and put a lot of effort into making them user friendly. They understand usability. And that different users have different needs.
It’s better to learn how to do it in your own environment, than having to learn a whole new strange environment. Especially one that is not user friendly, with poor visual feedback, intolerant of any mistype, and requiring memorising.
For many people it’s not quicker or easier. If they’ve not used CLI before, they’d need to learn multiple new things. Going to a Web browser for help every time, before doing something is not quick. Memorising precise command strings that mean nothing to the user, is not easy for many either. For them it’s bad usability.
Memorising does not need to be precise with a GUI, as you are given visual cues and can see the next step to click. You don’t need to remember precisely every letter or it fails. You don’t even need to remember the name of an application. The desktop app launcher shows you which apps you have installed. I often pin apps to favourites as a reminder. Some Appimage apps don’t appear in the launcher. I forget I have them installed and they don’t get used.
Differences between Desktop Environments are easily found when you change. As GUIs are in many users comfort zone. We use them all the time. People know their home environment, and differences need only just that discovering. Not a whole new environment.
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.
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.
Like many KDE apps, DigiKam can’t see a network share. Which is a real disaster compared to better systems. It works if you can somehow mount the NAS share. But for non IT people, due to some sort of UX blunder, it’s never been possible to permanently mount a share with any GUI tool. Despite Dolphin being able to see the share. The nearest I got was to install and run a program called Smb4k. This will temporarily mount the share. And needs to be running all the time. But it times out a lot.
It is hard if you don’t know you need to mount the share. How long should people be searching the web for, looking to access the share directly like some apps can do, when they have never even heard of the concept of mounting a share. Telling non IT people to use some command line or other nerdy hack, with magic words that fail if one single letter is wrong, to do what shouldn’t even be necessary in the first place, is typical gatekeepery that stops so many from using Linux. You might not realise what a huge barrier, such broken usability is, for non IT people. Avoid being part of that barrier.
In Dolphin, yes it’s very easy to access the share. Ideally, DigiKam would work the same way. As do apps in Windows. This is why I say mounting shouldn’t be necessary. Most computer users are not familiar with such methods. I guess you are not interested in usability. Don’t mix what you find easy and what other, non IT users will find easy. And they will have to learn every step that you already know. The command line fails hugely on usability, learnability and familiarity. As such other OSs don’t expect people to use it. And as such have the majority market share.
Yes, if direct access is not possible, there should be an easy GUI way to mount a share. I’d happily help with the UX.
You really have to put yourself in the position of a non IT user. They see a blank window with a blinking cursor. No hint at what to do. You know they have already chosen GUI systems. And for good reason. It’s over. The numbers are clear. Talk to usability insiders. As you have clearly shown you are not one. Many Linux devs have worked hard to carefully create desktop environments and Apps like Digikam, all GUI based. To give non IT users a chance to use Linux. And make it an inclusive and learnable OS. They hate it when usability outsiders scare people off by telling them to leave their familiar world into a strange and difficult place.
The terminal is nothing like familiar GUIs people use daily. To most, the terminal is strange and full of opportunities to mess up.
“so much faster by copy/paste”
It’s not faster when the user needs to go to a separate application first to find the instructions, then find the text to copy. And also search for how to use the terminal, and that it might be called Konsole confusingly. And also to understand if the command did anything. Does it print anything that you need to read? Should you close the terminal afterwards? Should you trust copy pasting from Internet strangers? All this is missing from online help, where they assume people have used the command line before.
Such a GUI app could be launched from Dolphin by right-clicking the share, and selecting a new option “Mount” that would help discoverability. A standalone app would need:
A clear title. Like "Mount Share"
A ‘Share selecter’ Browser.
The ‘mount point’ definition should have both:
‘Folder Browser’ for manual selection.
‘Default path’ option. Most don’t know where it should be mounted.
‘Credential definition’ needs a ‘Guest/Anonymous’ option for when there is no account defined.
Can the user choose? Not if there is only an appimage. Some devs don’t realise the problems they are causing doing that. So it is very important to enlighten them.
I agree with the OP. But swap the term “newbie” for “casual user” or “non IT user”, and more people would agree. Even the nerdiest IT Pro was a newbie whenever they use a distro for the first time. Avoid the term “normie” too, as people have different ideas of what normal is. There are more non IT, power users who have a deep knowledge of their applications, than all Linux users put together.
So this discussion is all around a sloppy choice of terminology.
But, for a non IT person, installing Linux, using the typical GUI tools is not specially hard to do. Write an ISO to a USB stick. Boot the PC. Answer the installer questions like language etc. And if something doesn’t work, try a different distro. The problems come when people suggest users use unfamiliar UIs, such as the command line or fiddling with config files, where, if you don’t know the exact magic words, it fails to work.
I’m feeling more tired about Windows, and the reason I haven’t switched yet to Linux is because I need some programs that only exist on Windows. But, at this point, I’m focusing on ditching these programs and finding alternatives for them…...
Yes. I’m happy with the performance of the Kdenlive video editor on my weedy laptop with no GPU, 8gb ram, running Kubuntu. I did 20+ hour long videos for a conference no problem.
Is it possible to use Linux without the command line?
We’ve all heard it before: People claiming Linux isn’t a viable alternative cause you can’t run it without using the command line....
Can You Use Linux Without the Terminal? (How to Geek article) (www.howtogeek.com)
digiKam, KDE's powerful photo managing software, reaches version 8.3.0 (www.digikam.org)
Don't use Appimages (a writeup about all the reasons they are a pain for users) (github.com)
Appimages totally suck, because many developers think they were a real packaging format and support them exclusively....
I made a plain text Linux cheat sheet as a reference and for beginners. (cerium.cc)
If you have any suggestions or criticisms, feel free to comment them....
I'd like to get away from "arch bad for new users"
When I say arch I mean the arch distro and all of its offspring....
In your opinion, which distro should I try to edit videos stably?
I’m feeling more tired about Windows, and the reason I haven’t switched yet to Linux is because I need some programs that only exist on Windows. But, at this point, I’m focusing on ditching these programs and finding alternatives for them…...