Even If you give me an OS with great and fast GUI, I would still prefer better CLI (Command Line Interface)

A man of culture as well.

K

So you would rather the long way round then, there some things terminals are best for but not everything like open a program 1 click instead of i guess going to programs directory then running.

@Kryptic0 well if youre good at it its simple and faster

@Kryptic0 GUI is also typo free and doesn't require to remember a command (in case you forget it, there is no autocomplete that can help) ... of course you can search it, but it will mean, more time wasted :)

(Mutes rant)

Then use Arch.

@dontbeevil actually there is autocomplete. Like in pgcli

pgcli.com

@Faraaz yeah i know, maybe i wasn't clear, i mean if you totally forgot or don't know a command, autocomplete cannot help

@dontbeevil buttons get lost in bad guis too. *cough* codeblocks IDE *cough*

No one cares if you prefer a better CLI over a worse GUI, it only matters if you prefer a CLI to an equally good GUI

@calmyourtities thats what I said, read better

@savethecode you said you would prefer a better CLI, over the good GUI, saying the CLI is better

@calmyourtities I said that no matter how good the GUI gets, I always prefer an OS with better CLI

@Kryptic0 rule of thumb: if it is common enough to be used as a one-click, it should be common enough to have a single command too.
Doesn't ever work the other way due to UI constraints.

That's why there is NO very good git GUI client to this day (best one is sourcetree but it's quite slow). If you want to get it done properly, there's always the terminal button -- that's a one-click that works.

@savethecode that could mean a better CLI over a worse GUI

All right, hipster hackerman, I'll stick to whatever makes the most sense ;)

@xsacha I don't know about sourcetree, but as I'm using VS is literally:
- 2 click to commit https://docs.microsoft.com/en-us/...
- 1 click to push https://docs.microsoft.com/en-us/...
- 1 click to pull request https://docs.microsoft.com/en-us/...
- 1/2 click to fetch/pull/merge https://docs.microsoft.com/en-us/...
- has a built in a merge resolver https://docs.microsoft.com/en-us/...
everything without change windows, remember/write command/branch names, resolve the conflicts some where else... this is "tested" in my previous company comparing speed and reliability with my colleagues that prefer CLI ... but anyway use whatever is more comfortable to you, just don't say what everyone must to use because is better (in your mind). (the last sentence is generic not referred to you)