3 ms·
It's much the same as not providing a command line for the original Mac, hence preventing text-based programming Not true. Stephenson even talks about this in
by gaius 17y ago
It's much the same as not providing a command line for the original Mac, hence preventing text-based programming
Not true. Stephenson even talks about this in In The Beginning Was The Command Line. It was called MPW and provided a very Unix-like experience (Makefiles and so on). The rival was THINK Pascal, and then later CodeWarrior, which were IDEs.
- demallien 17y agoI'm not entirely sure where you're trying to go with this. There was no command-line mode for the Mac. You couldn't take e.g. Wordstar (good grief, it's been a while since I last typed that name!) , and run it with little modification on a Mac. You would first have to write a GUI-based console for your text-only app to run in. There was no console SDK. Yes, it was possible to do, but as it would take as much work as writing the app as a proper GUI app anyhow, you might as well forget about the console.
- gaius 17y agoWell, you said there was no text-based programming, whereas I remember doing it... I'm pretty sure you could run your code in the MPW shell and use STDIN and STDOUT as per any C program of the time. CodeWarrior also had this, called WASTE there.
- pohl 17y agoCould you deliver that text program to the user such that they could compose it with others in a standard environment? I think that's the real point - that programmers were discouraged from falling into habits of older platforms.
- gaius 17y agoYou certainly could with CodeWarrior, I can't remember about MPW. And umm, of course programmers should be discouraged from falling into habits of older platforms. Otherwise the web would look like an IBM 3270 :-)
- ableal 17y agoAlso Lightspeed C, if memory serves, got in early dibs. Worked nicely, many fewer floppies than MPW. Was IDE, though. P.S. demallien is completely right. S.O.P. was to hang your code from the GUI event loop (skeleton samples provided).