[X] My Assistant

Personally i prefer GUI. In an integrated GUI tool, you only need to click several times and the function is called. (e.g. git cli and sourcetree) And GUI can also provide me with better visual feedback. (again e.g. sourcetree, i can view the whole commit tree and all merges of branches)

Why do you choose cli? Set aside the factors of deprecated mouse lol (IMG:[invalid] style_emoticons/default/tongue.gif)

Big dilemma since for other people's apps I always prefer them to have a GUI, so if any GitHub app is CLI-based, I always try to find a GUI for it (like Youtube-DLG, GUIllery-DL)
while for my own scripts (.bat in Windows or .sh in Linux) that I use to check my ping, make backups, auto-hibernate my system or reset network settings, I'm ok with using CLI

I have no programming knowledge, but it's the year 2025 man
I don't know what normal user would like to use a CLI, unless the app has no alternatives

Every time I have to deal with GUI I spend minutes trying to remember where is the right button.
With CLI program you open manual and search for keywords, that's it.

GUI is probably better 90% of the time.

For certain tasks Command line is better like with setting up stuff on a linux server or certain processing tasks where you need to set specific values and it can be run via a bat file.

"It depends"

I use nvim as my text editor. It is CLI. It is way more feature rich than lets say notepad.exe that would be GUI.

Honestly I don't much see the difference anymore with all the CLI applications being quite graphical as well. Hell, my terminal can show images in the "CLI" / text-based file manager/explorer.
(IMG:[files.catbox.moe] https://files.catbox.moe/hlg4dq.png)

But for file management I usually prefer either my zsh prompt, or an GUI window with fancy grids and tiling and all. Depends quite a lot on what I am doing.

it you ever want real productivity you want CLI not GUI, unless you are forgetful enough so that you can't even remember like 20 commands and use them well

I have no programming knowledge, but it's the year 2025 man
I don't know what normal user would like to use a CLI, unless the app has no alternatives

automation, also video encoding

Plus the startup time is usually much better on text-mode stuff.

There are times i want something graphical but usually I opt for command line driven stuff simply because it offers me flexibility for the things i want to do. I wouldn't want to do certain things in a text console, like most image editing - although for just resizing a picture that's a command line task.

For things that are done in many small steps, a graphical environment may be better, like cutting and mixing various audio tracks. Doable with ffmpeg and sox and others, but sometimes it's just not a very good way to conceptualize things. Other times, though, command line can offer a level of precision that is much more cumbersome to get in a graphical environment. Plus, good luck copying a bitstream without re-encoding when you're using a graphical video editor. That's something video editors just fundamentally aren't built around, but when you're splicing stuff together it can be useful to do so and you avoid generational quality losses.

Shorter answer: most of the time, CLI. But not 100% of the time. Maybe 90-95%.

This post has been edited by Moonlight Rambler: May 13 2025, 06:47

CLI is fast and clean, especially when you already know what you need to use.
It's my go-to for ripping media from sites for archiving and editing.