Yes. To a typist, it's all about the typing. The design, engineering and drawings don't seem to be important it seems.

Yes. Sure. I see. Thanks. Maybe I was too focussed. Non IT people are nerdy too.

Thanks. I've tried it. But it's not a permanent mount. The program needs to be running all the time. And it frequently times out. A very poor experience. Other OSs do much better.

Definitely a help website that focuses on user level questions and not IT pro solutions is desperately needed. Today new users are immediately given misinformation by hard core Linux techies with no clue about usability or user level solutions.

Windows users have a variety of different skills and experience. I guess the most likely ones to try Linux first are not going to be the PC-fearing ultra-causal users, who probably follow what their friends do. But the more adventurous and curious ones, or IT workers.

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.

"The command line is the natural way of interacting with a computer."

It's not natural at all for many people. Far from it.

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 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.

Go down that path and it's all binary. But users deal with metaphors. And containers are very useful.

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.

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.