For instance: A typical 2D drawing program which would primarily be used through the UI to draw images could also register new image format plugins with the operating system, so that all applications that deal with image files suddenly can load and save those new formats. The same application might be started on the command line in a 'headless' mode to offer image manipulation tasks like ImageMagick, and finally the application can offer an AREXX scripting port for more complex automation tasks, and "orchestrating" several applications.
All of this was standardized through "best practices" guidelines by the Amiga team.
I miss the Amiga :)
PS: My pet theory for the reason why there's a "shell renaissance" is that UI usability (in the sense of making complex application features "usable") has dramatically regressed in the last 10..20 years because the target audience for most apps has changed from active users to passive consumers. People who don't fit the "average user" have no other choice than to move to the command line because UIs are no longer designed for them. This "average user" targeted by UI designers is no longer a creative person who uses the computer to solve tasks or create art, but a passive media consumer. The computer has been degraded from the "bicycle for the mind" to a dumb TV set basically.
Tyranny of the Minimum Viable User
https://old.reddit.com/r/dredmorbius/comments/69wk8y/the_tyr...
(I actually used this feature recently when I wrote a Blitz Basic plugin for modern Emacs. It uses ARexx over the network to talk to Blitz, so you can write code in your modern operating system, and then compile and run on the Amiga running alongside in an emulator[0])
There were also a number of visual programming environments such as Amiga Vision and Scala which were marketed as "Multimedia Authoring Systems". They were used to create information kiosks, advanced interactive presentations and early CD-ROM hypermedia products such as multimedia encyclopedias, reference works and the like. I'm surprised there's nothing like them today, they seem ideal for the simpler end of the mobile ecosystem, or more cynically for those who want to turn their whole platform into unhackable (in both senses of the word) information kiosks.
Back in the 90s I looked at systems like this, or at Visual Basic, or NeXT Interface Builder (which later made its way to Mac OS X) and thought that the future would be some extension of these technologies, not the tottering stack of cli tools we use today.
I too miss the Amiga, and consider myself a proponent of desktop personal computing and "bicycles for the mind", which can be a depressing thing to be in these times.
The command line tools are simply more versatile and configurable.
We can try to take git clone command as an example and try to design a GUI dialogue which would allow to use all the options it has.
I think it is very hard and you will end up with something looking scarier than space shuttle cockpit.
I believe it'll take roughly the same time to make sense of that dialog that it takes me to quickly man git-clone to remind myself about some obscure option I don't use everyday.
I don't hate on GUIs, I just think that it is very hard to design full-featured GUI for complicated tools that we use every day. I would like to see an attempt to do this for Git, the key is being full-featured.
Prior to trying it I was a hardcore git terminal user. I still drop to the terminal sometimes, but magit has won me over for the day-to-day normal workflows.
You have to use Emacs for Magit, as it's an Emacs Lisp package, but it really is worth trying in its own right.
VisualAssist was a very popular plugin for it (don't know if it's still relevant) which added functionality inside the GUI.