-
-
- As I’ve read it, computer OS writers create a command-line interface, and then write a GUI based on that. Has there been any OS that was fully, exclusively created to run as a GUI only, with no command-line interface at all? Could Linux be re-written this way? - MC
-
In a way, Linux already has this capability. You can run X Windows and avoid the command line entirely. But there is always something you need to tweak manually, so you still need the command line.
The original MacOS is the classic example of an OS with no command line, it was exclusively designed to function through GUI only. For modern systems, I’m quite impressed with the way MacOS X hides most of the BSD functionality to the GUI, it is entirely invisible unless you’re dealing through the command line.
Having a single all-singing all-dancing GUI kind of goes against the Linux/Unix philosophy of small utilities that get plugged together with pipes. For example, say I want to see details about one running process, freecell for example. On NT I’d right click the toolbar to get a selection window, then click on Task Manager, the click on the tab I need, then sort the list to find freecell.exe. Due to the limits of Task Manager, there no way to filter the results to just see freecell. With a Linux command line I’d just type ps -ef | grep freecell and there the answer is!
Duh, the Macintosh, silly! There is NO command line. Some people have written some, though. But they’re not needed.
Well, up until but not including OS X, that is.
OS X needs some work; I routiney have to use the Unix command shell to do silly things that have no right being on a Macintosh. Sometimes I even have to login as {gasp} root!
Debian Linux (6-ish or so) installs such that you don’t ever have to look at a command line. But even with its long development heritage (for the computer world) it’s still nowhere close to Mac OS X as far as insulation from the “underlying” OS.
Linux is not written with a command line interface. It never has been. An interface of some sort is normally required for the average user, but all Linux (the kernel) does is make it possible for you to use your computer in a sane manner. When many people see linux, they might see a command line; this could be bash, csh, etc, etc. If you start linux and then directly boot X Windows, I suppose it could be considered running a GUI-only operating system. In fact, X Windows is just a program, as is any user interface.
er, I also meant to say that Linux, libraries, bash, etc, is rightfully called GNU/Linux, as linux distributions normally(always?) come with the GNU utilities. For more info and some ranting from the guy responsible for GNU, take a look at http://www.gnu.org.
I thought MacOS has had a hidden debugging command line prompt since System 6 or so? I’ve never had to use it, thank god, but I recalling running into references to it quite a bit.
Mac always had MacsBug, which was only accessible through the “programmer’s switch.” It was rarely used except for program debugging. If your program needed CLI intervention, it was broken.
On a similar vein, Apple always had Applescript, which allowed you to run CLI-type programs. Applescript shows some interesting promise, now that it’s integrated with Unix on MacOS X.
Yeah, but Macsbug’a not really a CLI… it’s really just a CPU monitor with some extra features. It gives you access to the CPU itself. Also, access to memory. Since ROM is memory, you could theoretically access ROM routines, but those are all Pascal toolbox calls – nothing you could realistically access from a monitor program. And the MacOS certainly wasn’t designed around Macsbug nor a command line.
Also, Apple’s not ALWAYS had Applescript. Before MultiFinder, there was really no reason to have AppleScript, since the OS wouldn’t multi-task! Plus, AppleScript isn’t the same as a command line. It’s designed for inter-application communication (mostly), and most of its functionality is done via applications that support AppleScript, or built-in AppleScript extensions that are programs that know how to talk to the OS. In a way, you could equate it with Visual Basic (using DDE or COM) on Windows. If anyone remembers REXX, it’s along the same lines.