3 ms·
Short: Every single Desktop Environment, then and now, does an absolutely piss poor job of abstracting away the need for a casual user to ever whip out the term
by Animats 5y ago
Short: Every single Desktop Environment, then and now, does an absolutely piss poor job of abstracting away the need for a casual user to ever whip out the terminal.
Yes. In the original MacOs, there was no command line. That was by intent. It was a decision Steve Jobs made. And it led to the popularity of the Macintosh. The Macintosh was not text-oriented internally. It was resource-oriented. You could tweak a lot of things using ResEdit. Where things were in directories was not too critical. The Finder would find applications anywhere, and they were self-contained in one file with resources.
This was elegant. It was a complete rejection of the DOS/Unix approach. Users loved it.
It suffered from some implementation problems that dated from the Macintosh's original floppy-based configuration. Writes were deferred too long and resource editing was very brittle. This gave resource forks a bad reputation, especially when applications wrote configuration and status into their own resource fork. Any abnormal program exit left the resource fork damaged.
When Apple took over NeXT, they got a system built on UNIX. So now they were stuck with the command line and the UNIX baggage again. They tried to keep the resource fork at first, but gradually gave up. It didn't play well with the UNIX file system model.
The Linux tradition is that GUI system tools suck. They exist, but try to do anything and you soon find you need to use a command line. The GUI tools are never complete, and they're often wallpaper over a command line tool. Often they don't really know what they're doing to the system; they're just creating commands and displaying the responses.
- michaelmrose 5y agoAll software and by extension OS are text oriented regardless of appearance. If you take a wad of human readable text and use it to built a binary blob then the blob is a function of the original program text ergo the text is still there just liable to be inscrutable. Classic Mac OS hot garbage. They switched because unix was a better basis for an OS than anything that could possibly have done with their existing OS short of throwing the hard drive containing it out the window and starting over. You can install a user oriented distribution like Mint or Ubuntu and never see a cli if you don't want to. So far as I can tell the gui tools that come with these distros are complete for all standard tasks. Minimal or technical distributions like arch, void, gentoo are pretty obviously meant to managed with the cli although users can still use rich gui tools for many non system tasks. Few are wallpaper over cli tools. I don't know where you got that idea.
- temac 5y ago> The Macintosh was not text-oriented internally. I'm not sure what you mean by this specific part; Windows is not "text-oriented internally"; neither is let's say Gnome. Actually if that's about how often e.g. DOS commands would be run by various GUI elements, it was likely even less a practice on Consumer Windows than on NT based systems, given the DOS command window was a VM with limited and/or weird interactions with the host OS.