Copland/Gershwin vs. NeXT 147
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."
A well-written article (Score:3, Insightful)
The tragedy is that those who most desperately need to learn the lesson presented here (that would be the uninformed, inflexible PHBs) will never read this kind of article, or if they do they will never realize that we're talking about you, here!
It's just amazing how many technology "managers" cannot comprehend the silliness of mandating a schedule and a feature set. You might get it by then, but it will be a piece of #@%$.
Inaccurate in places (Score:5, Insightful)
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.
Article is one big rant (Score:4, Insightful)
Hey, I'm an engineer and I think it takes everyone on a project to make it fail. On successful projects you have only 10% of the people doing all of the work and fixing the other people's mistakes... most projects succeed in spite of bad management or bad subsystem X.
Mac OS was on a death march because of the fundamental underlying technologies and a culture that was stuck in only one way of doing things... and windows is on a similar death march. OS X takes technology from the UNIX way of thinking and from the NeXT way of thinking to make a platform that is a developers dream. I think this is what puts OS X beyond Windows and will eventually lead to new "killer apps" that will save Apple. I really doubt that if Apple had went with Copland so many alpha geeks would be flocking to Mac... I doubt slashdot would have added an Apple page or O'Reilly would have a macdevcenter.
Hindsight (Score:5, Insightful)
Re:Inaccurate in places (Score:3, Insightful)
Who was fired (or otherwise bitterly parted ways) from Apple after apparently mismanaging a major development project.
Apparently at least in one case, the PHBs he's ranting about are him.
Not to say he's worthless, but he does fit the general description "Apple basher". He needs to let go of his bitterness and get a better perspective on things.
Re:miracles (Score:2, Insightful)
Remember though, at the time BeOS had some gaping holes, such as printing. There was some amazing technology there, but Apple was much more strongly tied to print design than today (with the huge internet focus).
They'd likely have had much more work to do integrating an immature BeOS than it was with a very mature NeXT.
I understand that there are a couple of BeOS engineers at Apple now, let's hope we can get some of the very cool ideas that are now dead (replicants, instantaneous searching, semi-sane metadata, etc.).
Re:OpenDoc (Score:1, Insightful)
OpenDoc worked on the "container" concept, so once you had an application that was a "container" app you could paste in OpenDoc parts and use them as part of the master document.
Far as I can remember, the only OpenDoc applications that even appeared were Cyberdog and Nisus Writer. It was a real shame about Nisus Writer too, since they expended so much energy on OpenDoc hoping to ride the wave and Apple pulled out the rug (they still don't even have an OSX version).
Imagine if it stuck though, OpenDoc graphing and charting applications you could paste into Nisus, drawing objects drawn in your favourite program still being editable by it, tables and indexers, oh well.
Disaster in success (Score:2, Insightful)
The author seems to assert that a fantasy completed Copland and OpenStep would be of equal value. But imagine if Apple had actually shipped Copland. What would Apple have had? It might not have crashed as much, but it would have been just as obscure.
NeXT brought Apple Unix roots. This has completely changed the market perception of Apple. Folks and companies who never would have considered Apple are now testing the waters.
It may have come about because of confused decision making, but thank goodness it came about.
We needed the Unix (Score:4, Insightful)
Unix gave the Mac credibility from some key market segments. It gave the Mac mindshare. If we chirped about OS 9 having preemtive multitasking, people would've said "about time" and rightly so. As it stands now, the Mac is now buzzword compliant and, more importantly, it has the time tested core of Unix and all of its familiar tools that scientists and sysadmins love.
Re:Disaster in success (Score:2, Insightful)
I wholeheartedly agree with this.
I've been a staunch Mac user/advocate for about 7 or 8 years. I first started mucking around with linux in 96-97? and later moved on the Free/OpenBSD. I eventually I got hooked on the UNIX thing and became regular command line jockey and would always have a a few ssh sessions open on my mac at any point in time. I probably would have lost some interest in the Mac if they wouldn't have gone the NeXT/UNIX route. first I started playing with apache and FTP, then BIND, then sendmail, then samba, now apache/php/postgres/oracle. Odds are I wouldn't have been able to run those on whatever Copland/Gershwin would have produced. just like you can't usually run that stuff on OS 7/8/9. The OS is usuall just a bit too strange to make porting very easy. I don't think I would have dropped the Mac in lieu of windows to occasionally run some commericial software but I also don't think I'd be as excited about the OS/hardware as I am now with my Powerbook and OS X and it's ability to easily(relatively speaking) compile/run just about any popular UNIX app/server in addition to all the commercial wares. So if a really staunch Mac supporter would have possibly lost some interest, I seriously doubt apple would have seen all the interest from potential Linux/UNIX "switchers" checking to see if the grass is greener on the other side of the fence.
Re:nostalgia (Score:3, Insightful)
When objects are autoreleased, they are GCed at the end of the event loop.
This is much better than, say, Java, where you can never predict when GC will occur (and I've spend countless hours trying to get a product to work even though it will randomly stop and check EVERYTHING IN MEMORY to see if it should be deleted.... when doing a large server with gigabytes of objects in memory this impact is a major PITA) With objective-C memory management is semi-automatic. A better solution than Java and FAR better than C/C++.
I don't know what you mean by "real exceptions" but basically, every languages has its differences and the person I was responding to was just wrong in saying that Objective-C is a pale ripoff of smalltalk.
Re:A well-written article (Score:3, Insightful)
Anyway they realize generally in about 6 months, not that they will ever call you up and admit but next time you see them (oh and they might bring you back to consult) you'll be able to tell. Anyway if its any consolation the guy who fired you has just taught all his employees to lie to him. From this day forward he never gets the truth about anything and his productivity hits the floor.
One of my great hopes for this country is the end of MBA running everything. I'd love to see the CEO of soup company be a guy who did soup his whole life and the CEO of a car company be a guy who either built or sold cars his whole life...
Finally, you might have wanted to mention where you live in your last line.
Re:Subjective Article (Score:2, Insightful)