KDE way versus the CLI way

[woodsmoke]

THIS IS NOT AN INSULT TO CLI PEOPLE...

THE CLI PEOPLE ARE WHO KEEP ALL OF LINUX GOING...

BUT...IN TERMS OF ...THE

new to Linux...

new to... kde USER...

there is another thread that was resolved by addressing certain "daemon" support... to wit:

if you have daemon.conf configured correctly, it should work fine.

This is NOT about "how good KDE is" as opposed to how "elegant CLI is"...

THE QUESTION IS...

HOW MUCH OF KDE IS BEST ADDRESSED

a) through a step by step instruction about going through the "symbology" / "menu structure" of KDE plasma

as opposed to:

b) "here ya go, type this into terminal"

THE WOODSMOKER USES THE TERMINAllll...!!!!! AARRGGHHH...

this is not about "good" or "bad" or "smart" versus "newbie"...

it is a REAL QUESTION...

FOR THE NEW USER...

a) how much is BEST ADDRESSED WITH CLI...it is the BEST way to address "a problem'..

b) how much is BEST ADDRESSED WITH A STEP BY STEP instruction concerning the symbology / menu system of KDE

IN OTHER WORDS...

TO DEFUSE THIS...

it is not about "good or bad" or "people need to learn this"...

WHICH THINGS..."what stuff"...

is "best done with a menu system"...

is "best done with CLI"...

WE ARE NOT DISCUSSING THE "learning of CLI" or the "learning of KDE plasma / menu system"...

it is about WHAT PARTS are BEST ADDRESSED by...CLI or "menu/KDE"

wood...just asking a question ...smoke

[Bings]

GUI as much as possible. Most computer users are only comfortable using GUI and if computers were CLI only, they'd not use them at all

[GreyGeek]

I prefer CLI when ever possible (and IF I can remember the switches without having to pour over man pages) and the primary reason is because the terminal is faster than the GUI. However, that said, I've just upgraded to Plasma 5.13.0, which I understand is very fast. If it is fast enough then I will probably do less CLI and more GUI. I'm hoping that to be the case because the old gray matter isn't working as fast or as accurate as it used to at 77.

[claydoh]

I side with wooddy here, but mostly on principle. I use the command line where appropriate, but the overt reliance and the focus on it being always superior always every time is a put off for many.
Sure, it is simpler and safer, as well as Desktop agnostic to use a command, but we never really explain the command all that often, and we usually fail to take in ti account a user's possible experience and comfort level.

I have been guilty of this laziness myself, and quite often.

[claydoh]

I prefer CLI when ever possible (and I can remember the switches without having to pour over man pages) and the primary reason is because the terminal is faster than the GUI. However, that said, I've just upgraded to Plasma 5.13.0, which I understand is very fast. If it is fast enough then I will probably do less CLI and more GUI. I'm hoping that to be the case because the old gray matter isn't working as fast or as accurate as it used to at 77.

i will disagree with that, as I just upgraded my neon system to 5.13, via the updater systray icon. Couple of clicks and a password.
VS a few up arrows in my terminal window and a password
VS su-tab apt up-tab then su-tab apt fu-tab

I'll update my Kubuntu box the same way once it is pushed to the ppa

[jlittle]

I use the CLI all the time. I often use quite complex one liners. But I prefer GUI apps when they suit the task; for example, I prefer the K help centre for looking up man or info pages to typing "man whatever".

But the CLI is much better when things go wrong; for GUI apps to handle problems effectively the developer has to anticipate them. But problems are often, if not usually, unpredictable.

Regards, John Little

[woodsmoke]

Nicely developing thread,. thanks guys!

Keep the comments coming folks!

woodsmoke

[Qqmike]

I prefer GUI.
KISS
(for those non-natives, or those not familiar, or non-engineering/science grads: "Keep It Simple Stupid")

In my defense ... I've programmed from machine language to higher-level and special-purpose languages, I wrote an intro CLI how-to (for Kubuntu users here), and so on. But at this age and stage in life, I just wanna "get there." I can't remember half of the details (e.g., switches, lengthy commands, etc.) in my how-to, and when I do have to use CLI, I have to refer to a cheat sheet or reference my how-to or bring up a man page. I am impressed, though, with some of jlittle's lengthy and subtle-complex commands!

[GreyGeek]

Qqmike, you said what I wanted to say, but much better than I did. Spot on.

[TWPonKubuntu]

Good question woody, thanks for asking.

I use both CLI and GUI/menu.

If I don't know of a GUI which does what I want, I'll dig into the docs and man pages to find the CLI commands.

Once I'm familiar with what steps are taken by the CLI, from what is displayed in Konsole, I still watch the process for any glitches.

If I discover a GUI which does the process I want, I tend to use the GUI and just let it "do it's thing". That means I have learned to trust that particular GUI.

As an example; I use CLI to run upgrades with apt, on a daily basis, BUT I also run 'program manager' because there have been a couple of incidents in which the GUI program manager Missed an item. I'll admit that this may be because the item was just recently added to the repository and did not get cataloged between the CLI run and the GUI run. I have no way to check that, but it is a possible explanation.

Again referring to package upgrades from the repository, I assume that both apt and my program manager use the same set of repository sources. They should, but I'm unsure that they always do so.

So, I'm mixed, some CLI and some GUI. Much depends on if I have the time to watch a CLI process in Konsole or if I want to go do something else.

[jglen490]

While there are certain types of activities that are very focused on one goal that are very appropriate for CLI, I prefer GUI for most of my Linux action. And before someone jumps my case about how simple it is to combine commands and to script on the command line, I'll say that you are right. However, be aware that most GUI products are the result of scripting along with building compiled and linked objects from source code. It's great if you know how AND are well practiced, otherwise who cares.

I have built and actually run simple operating system elements, and I wrote a menuing system (in compiled C) for our very poor elementary schools who had nothing but donated old x86 machines with no Windows (3.0 or 3.1) licenses included or available. Years ago ...

[MoonRise]

I prefer GUI.
KISS
(for those non-natives, or those not familiar, or non-engineering/science grads: "Keep It Simple Stupid")

In my defense ... I've programmed from machine language to higher-level and special-purpose languages, I wrote an intro CLI how-to (for Kubuntu users here), and so on. But at this age and stage in life, I just wanna "get there." I can't remember half of the details (e.g., switches, lengthy commands, etc.) in my how-to, and when I do have to use CLI, I have to refer to a cheat sheet or reference my how-to or bring up a man page. I am impressed, though, with some of jlittle's lengthy and subtle-complex commands!

actually have to +1 that one. On occasion I do use the CLI when there is no GUI that I can readily find. I actually use BASH History quite a bit but really I prefer the GUI for the reason stated above.