Good GUI are hard to make while a good cli is rather easy.
Nothing wrong with a GUI that does what it needs without fluff.
this post was submitted on 12 Feb 2026
1228 points (97.7% liked)
linuxmemes
30501 readers
1170 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
The cli has one other benefit which I think is rarely recognised: it's pretty easy to tell someone you need to run "xyz -a -b -c" (bringing the safety risk with it to be fair), but it gets a lot harder to be like "so in the top left there is a cog button that opens a panel on the right where you're looking for the 2nd tab and there'll be a checkbox".
The things I appreciate even more than a good gui are programs with a good gui and a cli.
It is very easy to tell someone type this and shut up. I've never seen an explanation of why -a -b and -c are necessary or what they do. Although I recognise that a lot of people just want magic, and running "xyz -a -b -c" is the next best thing.
I would love to see what cli commands the gui uses, they would be much easier and faster to learn.
That's one of the things I like about yt-dlp-nis on android. You can select all the options you want through the UI and grab the resulting yt-dlp cli command.
load more comments
(7 replies)
load more comments
(4 replies)
Tbh a lot of things are just easier to show/explain with images and icons in addition to text.
And in many cases mouse control is just super handy and fast
And while a terminal can show all these things⦠its just not comparable, IMO.
I wouldt want to write my job application in the terminal, or design a product, or whatever else requires just a smidge of graphics
I'm just a faster typer and when I have to go back to the mouse controls I feel sluggish. Of course, the right tool for the right job, I will never find myself with a tui to manipulate 3D objects or editing images but I will go to vim for editing documents using latex
load more comments
(1 replies)
load more comments
(3 replies)
So true. I mostly live in the embedded world but have had to write GUIs from time to time, mostly to connect and send commands to some sort of embedded device.
I always start with a cli version for testing and then write the GUI. A quick wrapper around the comms library and Iβm done.
But there are so many annoying fiddly little details in the GUI to deal with that it usually takes as long just to write the GUI as it does the entire rest of the code. Layout, menus, tooltips, icon choices, dealing with screen sizes, DPI, resizing windows, responsive data, etc.
Edit: A simple example that Iβve dealt with many times is reading and writing config data. For the CLI version itβs typically two commands:
βtool read_cfgβ reads from the device and prints the config to stout
βtool write_cfgβ reads a config from stdin and sends to the device.
Add a β-fβ option to use a file instead of stout for people that donβt remember how to use redirects. Add a couple of documentation sentences to the help command. If there are any issues, print them to stderr and bail. If the user wants to edit the config they can use whatever $EDITOR they prefer.
The same functionality in a GUI means that you have to first implement an editor for values. In my case that was generally a bunch of nested key/value pairs so I could probably find a widget that would work. And then understand how it handles being resized, gets styled, uses tooltips, etc. Of course there would need to be some code to get the data into and out of that widget which would probably need massaging. Then I need to let the user know if there are local edits. And then there is the fact that the data is now in three places, on a local disc, on the device, and in the editor and I need to communicate with the user that there is a difference between loading and saving from disc vs the device. Do I give a warning that loading from once place will overwrite anything theyβve changed in the editor? How do I make the four load/save buttons have obvious icons? And how to handle errors? An annoying pop up? Partially load the data? Something else? So many little things that have to be designed, implemented, and tested.
load more comments
(1 replies)
I think people are just too rigid sometimes. Some workflows are better in GUIs, some are better in CLIs. They both have upsides and downsides depending on what you're doing, and it's totally fine to prefer one to the other. Just don't let your preference keep you from learning and using other great tools!
personally I think having that all cli all the time phase is really important for a developer. Those that I've worked with who exclusively use gui's just don't have the same understanding of their system. Which is maybe fine at a certain level but not for a senior dev
I usually take the which does it faster route. Most of the time, cli wins, occasionally gui is actually faster
Can we add repeatable? CLI is repeatable and self documenting with nothing more than a text editor.
GUI? Good luck with that.
Seriously! I can do shit in the terminal, but I grew up post DOS and it's nice to just click something and have it work.
Meh, I mean you are not wrong.
What is even better though is knowing that whatever you click on is just inputting a command you could do yourself manually into a terminal. Now that is some cool full circle shit that Windows fucked up by hiding the CLI.
I remember waaaay back in the server 08-08 R2 days, you could do something in server manager (such as installing a role) and while that process was running, you had the option to see the powershell command it was running in the background. That was pretty cool
load more comments
(1 replies)
load more comments
(1 replies)
That's totally fine. GUIs let us theme our terminal windows, tile them, jiggle them around, maybe even make them wobbly!!!
Compiz intensifies
:) Did you know KDE also does wobbly windows?
No, I've been GNOME peasant since Ubuntu switched to it from Unity. Now also using it on Debian. Some day when very bored, maybe in retirement I'll try Plasma again. π
load more comments
(1 replies)
load more comments
(3 replies)
load more comments
(1 replies)
This is the energy we need.
New comers should never ever see or require a terminal.
load more comments
(4 replies)
I'm undecided with modern GUI because most modern software is just a web page now. And it will offer you a choice between boring light mode and boring dark mode.
I miss the days of GTK2 with hundreds of themes. It was one of the main reason I switched to Linux; the customization. I don't know how many hours I must have spent on gnome-look.org. Now I don't even bother to try new themes and just use Fluent-Dark. My desktop is boring and looks like everyone else that has a dark mode. I really really miss GTK2 and all my favourite themes I can't use anymore. I tried making my own and played around with Oomox but it's not the same.
But one thing that I do prefer to be GUI now is IRC. Now that there are web clients (sigh) that can display images and videos directly in the channels, chatting in text mode only is kind of annoying with all the links we are sharing.
load more comments
(2 replies)
I can and will terminal things, but the GUI is there so why not?
before I made the switch to Linux I never used a terminal. never. hell on Windows I even used a GUI for Git. I used sublime text as my IDE. if it wasn't a GUI I was lost.
Then I switched to Linux and it forced me to actually sit down and learn the terminal and now...now I have a hard time using GUI's. If something has a CLI or TUI option then I go for that over a GUI. like everything even my music player and video player. my IDE of choice now is DOOM Emacs. my file manager is Yazi. for Git I either use lazygit or just straight up the command line. but for everything else it's just so much faster and in the long run easier to just use the terminal.
All that being said if you like GUI's then hey more power to you and that's fine. that's the beauty of Linux. you run your system how you want to and don't let others tell you otherwise. Hell I know a guy that uses NixOS and doesn't have anything installed other than git and comma. he runs everything via comma. literally everything.
load more comments
(1 replies)
I like GUIs but I also like automation. Give me a nice simple GUI but also give me a way to run from a bash shell so I can automate functions based on complex conditions and/or a schedule.
load more comments
(1 replies)
If you
- need discoverability, or
- don't need anything composable
then sure GUIs are great.
load more comments
(4 replies)
The thing about CLI is that everything is hidden by default. You come to the application with your own mindset and a goal in mind and you figure out how make it do what you want.
When there's a GUI, you often see everything that's possible from the start and so the application dictates how you use it.
Though, you can do either with CLI and GUI as well. That's the sweet spot I think is the best. I love it when a CLI app guides the user through a process and gives options. And a good GUI should disable OK buttons and show validation errors if not everything is entered correctly.
In a perfect world, every app has a CLI mode, interactive and non interactive and a GUI mode with full validation and responsive UI changes. But realistically, good UX is what we need, either GUI or CLI.
load more comments
(3 replies)
An original confession bear post? Out here in the Lemmy wilds? Excellent.
I still do updates and most package installs through my terminal, but anything else I look for a GUI solution. I'm lazy.
In the same way some GUIs are trash, lord have mercy some CLIs are trash. Things like adding two verbose flags makes it extra verbose. Things like the parameter order mattering. Yeesh. It can be rough. It really varies tool by tool.
load more comments
(4 replies)
If we want the year of the Linux desktop to actually happen we need to have good GUI tools for almost everything. The second you say "command line" most people's eyes glaze over and they say they'll stick with Windows. Believe it or not guys, most people just want something that functions out of the box and they don't want to mess with it.
I like GUIs if they aren't web browsers pretending to be a desktop applications.
I do too.
They are good for discoverability, but suck when you have to do the same thing 5 times.
-- signed, a guy currently having to use a GUI to update the firmware on 5 headsets, and put our standard settings on them
load more comments
(3 replies)
A well designed GUI should give you fast access to what you need and allow you to get things done easily.Β
Nothing wrong with that at all.Β
It's pretty cool how both GUI lovers and terminal enthusiasts can have a great time using Linux
load more comments
(1 replies)
Everyone else is like: is it git checkout -b or git branch --set-upstream-to?
I like GUI's, but I prefer them simple and customizable, so I eventually want to switch away from KDE Plasma to just some window manager.
load more comments
(1 replies)
Thatβs legalβ¦ for now.
view more: next βΊ