Name one thing that a GUI program can't handle, I dare you. Me, on the other hand, I can point you to a trillion dollar business that uses only GUI and not a single CLI, to say the least.
Name one thing that a GUI program can't handle, I dare you. Me, on the other hand, I can point you to a trillion dollar business that uses only GUI and not a single CLI, to say the least.
> Me, on the other hand, I can point you to a trillion dollar business that uses only GUI and not a single CLI, to say the least.
No you can't. There are 5 companies with a market cap over a trillion. We can easily rule out Apple, Microsoft, Amazon and Google as they have all developed CLIs.
That leaves Saudi Aramco. Doesn't take long to see they have openings for CLI heavy jobs.[1][2]
Aside from that being an entire industry as opposed to a single company, are you not aware that BigCo games generally contain a developer console of some sort? Even the ones that don't provide end user access to it still usually have one buried somewhere.
Plus many of the dev tools for manipulating assets are either CLI based or have one integrated ...
- Optipng
- ffmpeg
- sox
And so on.
Pipe input/output between programs. Chaining cli tools is essential for my work and personal usage.
> Me, on the other hand, I can point you to a trillion dollar business that uses only GUI and not a single CLI, to say the least.
That's observably not true. Why didn't you just type out the name?
And even though the game industry primarily makes GUIs, it still uses CLIs everywhere in the development process, so it's pretty silly to say that it "uses only GUI and not a single CLI." And the console that's present in just about every game doesn't seem very "graphical" either.
A CLI represents that structure by accepting textual commands and presenting output textually.
A GUI represents that structure by displaying objects graphically, showing their spatial representation and connection.
And, traditionally, a GUI tends to show more structure up front while a CLI simply prompts you for a command.
The distinction isn't perfect, but a text adventure game is well inside the CLI camp.
2. Every single company in that industry uses cli tools.
Both assertion from your original statement are incorrect. What’s your beef with the command line anyways? It’s just an interface.
Get-ChildItem | Out-GridView -output multiple | Format-Table
There is a GUI with piped input, and piped output, which can be used to filter the pipeline objects using ctrl-click to multiple select "I want this, this, and that" in a view that is sortable and filterable.Here is a simple task which can easily occur in business: you have a folder with thousands of files named somewhat haphazardly. Copy all the files with have numbers 2011 to 2019 anywhere in the filename to an usb stick.
I would search for "2011 2012 2013 2014 2015 2016 2017 2018 2019", select everything that shows up in the search results, and copy those to the USB. Wonder what I'd do with millions of files though.
So just because companies have proven that GUI is successful and capable, it's still possible that it "can't handle" a lot of things nearly as effectively as CLI in some cases.
firefox (find . -type f | shuf -n10)
I doubt your computer comes with a GUI program that can do that for you. My point is that CLIs can easily be plugged into each other whichever way you want, but GUIs (except in some niches like audio) aren't built that way for some reason. find ~ -iname Makefile -exec sed -i ´s,-g,,g´ {} +[1] https://docs.xfce.org/xfce/thunar/bulk-renamer/start