Slashdot Mirror


Copland/Gershwin vs. NeXT

Etcetera writes "David K. Every (of MacKiDo fame) has written an interesting article at iGeek about Copland vs. NeXT and the decisions that Apple made back in '95-96. Although most agree that bringing Steve Jobs back was a Good Thing, a lot of cool Apple-invented technologies got left by the wayside without a fair shot at proving themselves once NeXT came in. Was it always the right call? Functions as a cautionary tale about management vs. engineering as well."

5 of 147 comments (clear)

  1. OpenDoc by georgewad · · Score: 5, Interesting

    I worked with a Software Engineer who worked on OpenDoc, which was about the only good thing aside from QuickTime that Apple had put out in that era. Some of you might remember the demo of an ActiveX control running inside an OpenDoc container. When NeXT took over, they hacked OpenDoc to run within NeXT's ojbect model. The Steve (himself) just said no, NeXT's object model is better. That's when my friend left Apple. Can't say that I blame him. OpenDoc had a lot going for it.

    --
    Karma: It's not just a good idea. It's the law.
  2. Inaccurate in places by bnenning · · Score: 5, Insightful
    I'm glad this article showed up here, I tried to post a reply on igeek when I saw it yesterday but it wouldn't let me for some reason. Anyway, Every has some good points, but also seems to have a strange hostility toward NeXT technologies which causes him to make some odd statements. Specifically this:


    So Carbon on a new kernel (NuKernal) was done long before the rest of OSX was ready. It took years to get NeXTSTEP and Cocoa and the rest of the OS time to catch up


    This is just absolutely false. The NeXT kernel (Mach/BSD) and Cocoa were ported very quickly. Apple bought NeXT at the end of 1996, the first Rhapsody developer release was ready less than a year later, and Mac OS X Server 1.0 shipped in early 1999. The reasons why the "real" Mac OS X took longer were that Apple had to implement Carbon for developers unwilling to convert to Cocoa, and write a brand new display system (Quartz) after Adobe dropped Display PostScript.


    NeXT delivered on its promises, it's just that Apple's requirements changed. And it's also worth pointing out that Mac OS X is a far better system than what was envisioned for Copland. Aside from the much better adherence to standards, it is a much cleaner architecture. From what I remember of Copland's documentation, it had a weird form of partial memory protection where the entire GUI ran in a single process, so any app could take down all other UI apps, although server processes would be protected. The transition to a fully buzzword-compliant OS wasn't going to happen until Gershwin, and I seriously doubt that could have shipped by now.

    --
    How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
  3. Hindsight by fm6 · · Score: 5, Insightful

    Ain't hindsight great? It allows you to sound wise without producing any testable arguments.

  4. it was a sad day when copeland died by talisia · · Score: 5, Interesting

    As I remember the events of the summer of 1997, Apple would have fallen apart if Steve Jobs had not come on board. At the time, people were leaving Apple left and right. Scott McNealy suggested that Apple should abandon MacOS and start selling java based network computers. The pundits were suggesting that Apple should abandon all things Mac and sell PC clones. I like OS X. I use it every day, but I have to wonder if Apple hadn't abandoned Copeland, if today I would be using an operating system more in the spirit of the original Macintosh. OS X feels like Unix with a bunch of pancake makeup on top. Instead of being simple like pre-X MacOS or BeOS, it hides its complexity from most of its users. For all the strength that OS X brings to the Mac platform, it brings along a fair amount of baggage too. It just doesn't feel quite right. There is something disharmonious about it. I'm having a bit of trouble explaining it, but I wonder if an OS built from the ground up for the Mac wouldn't have been better,

  5. It wasn't just the software by automandc · · Score: 5, Interesting

    I worked for Apple in the mid-nineties, when the PPC was new. I watched the entire (almost) death-spiral with particular interest.

    I think the article is good, but it is only half the story. Apple is, and always has been, a hardware company. The thing that really screwed Apple during the Gil Amelio years was a total lack of hardware engineering. Apple tried to become a "beige box" company, and tried to have a solution for every problem. It just wouldn't work.

    When Steve Jobs came back to the company, there was something like 85 SKUs for hardware systems. For those who aren't familar with marketing/retail, that's a lot. It wasn't like "You can have a 7200 with X Y or Z memory", it was "You can have a 7200 with 16MB, or you can have a 7200 with 32MB or you can have a 7200 with 64MB" and the vendor would have to stock all three. Impossible.

    Plus, none of the hardware was exciting. People just plain didn't want to own it. It was like, sure, I can get a beige box that runs 7.5.2, crashes all the time, and has only Word 6 (god, what an abomination), or I can spend half as much, build my own Wintel, and get the newest Office.

    The main thing the reintroduction of Steve Jobs did for Apple was put a single vision back in charge of both hardware and software. Even if Copland was further along than NeXT, it was hopelessly mired in a hardware development cycle that was just flawed. One of the main problems Copland faced was not only the need for backward compatibility of software, but the need to support 85 different configurations of non-industry-standard hardware. Impossible. Anyone remember the "Enablers"? God, what a mess.

    One of Job's most controversial moves, and perhaps his smartest, was to draw a hard line in the sand at the G3, a processor that was barely even shipping when he announced the spec. Thus, he promised hardware compatibility only back to the currently brand-spanking new machines, guaranteeing that, at the end of a 3-5 year development cycle, the OS would only have to support hardware 3-5 years old. Man, did people scream and moan ("But I just bought an 8600/120!"), but now Apple is back where it needs to be. One of the biggest complaints over Win2K was its trouble with older hardware. MS was able to make Win2K fly by (1) not pitching it to home users, who were more likely to have funky sound cards, and (2) providing a lot of expensive support to hardware manufacturers to write compatible drivers in time for XP.

    One pre-Jobs hardware move that Apple took that is now reaping benefits was to eschew its own good but expensive standards for adequate but cheap industry standard. Internal SCSI 4X CD Roms gave way to ATAPI; NuBUS gave way to PCI; etc. This made it even easier for the OS developers to support hardware.

    Anyway, in order to understand the whole Apple picture, you have to consider the wretched state the hardware side was in in 1996, and realize that, even if no one bought the cube, they have come a really long way - and that is what made OSX possible.

    --
    I'm a lawyer with excellent karma. Something's gotta be wrong.