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?
Get-ChildItem | Out-GridView -output multiple | Format-Table
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.