From: Cameron Kaiser <spectre at floodgap.com>
> I do remember a true command-line
environment for C program
development
> on the Mac. I believe Apple's came with
one. There were probably
others,
> maybe Manx. "Programmer's
Workbench" comes to mind, but I'm not sure
if
> that's it.
The full name was "Macintosh
Programmer's Workshop" It let you use *nix
style development tools such as yacc, patch and grep, and gave you a CLI
to
the compilers and linkers. Also, the colon *was*
the internal path
seperator
for the Mac, just like / in *nix and \ in MS-DOS.
Also, don't forget that every PCI-based Power Macintosh could be forced
into
OpenFirmware. People have designed elegant applications to run in this very
minimal but powerful environment.
Hi
It is too bad Windows and the PC group didn't continue the OpenFirmware
concept. This is the dominant reason why Windows takes so long to boot.
It basically has to hunt for hardware by timing out rather than not seeing
any boot configuration code. It was a bad move that has cost millions if
not billions of dollars worth of lost productive time.
Dwight
_________________________________________________________________
Hotmail to go? Get your Hotmail, news, sports and much more!