Yeah, I have terrible experiences with codewarrior as well. I had one programming class in the late 90s that required macs and boy did that make me hate macs with a passion.
But I dont think it was purely a codewarrior issue. The overall apple OS at that time was simply terrible and 10 years behind windows (i wont even count how far behind unix they were) -- they still could not get multitasking to work right. Which meant that any pointer error causes your computer to hang. And when you are coding for a data structures class in C all of your errors are pointer errors.
So I am sure a lot of developers abandoned the mac platform around those times, but maybe many of them are coming back now.
Re:Apple's Mistake
by samlittlewood on Thursday November 19, 2009 @04:16PM
(#951126)
Unfortunately, CodeWarrior was still way better than MPW (Macintosh Programmer's Workshop) - that was pure pain.
Re:Apple's Mistake
by steveklabnik on Thursday November 19, 2009 @05:48PM
(#951356)
Oh man, I had so many CodeWarrior shirts... "Blood, sweat, and code," "X Rated" for their OSX version...
I'm pretty sure that it was dominant at the time. I remember reading a lot of examples that used it.
Re:Apple's Mistake
by YuriNiyazov on Thursday November 19, 2009 @02:47PM
(#950929)
The relevant times under discussion are: the era of the Apple II which came with built-in Basic, and the era of post-OSX but pre-iPhone
That said, with OS X they really became a lot more developer friendly just because they adopted a UNIX base. At this point, I'd say they're the default platform for ruby/web development. Look at all the rails job postings for small startups promising 30" Mac Pros, etc.