In fact when Jobs first arrived back at Apple, "objects" was (apparently) http://arstechnica.com/staff/2008/04/rhapsody-and-blues/ http://arstechnica.com/staff/

In fact when Jobs first arrived back at Apple, "objects" was (apparently) http://arstechnica.com/staff/2008/04/rhapsody-and-blues/ http://arstechnica.com/staff/2008/04/rhapsody-and-blues/ still his intended way forward: 'The defining event of the Jobs 2.0 era relationship between Apple and Adobe was the creation and subsequent scuttling of the Rhapsody project. Rhapsody was Apple's original plan for a new operating system based on the recently purchased NeXT technology. Rhapsody's proposition for Mac software developers was simple: write your applications using these NeXT-derived APIs. These are the APIs that eventually became Cocoa, and there was much to recommend them even back then. But for Mac developers with substantial existing code bases, the proposition was more aptly phrased, "rewrite your applications using these NeXT-derived APIs." It was a hard sell, to be sure. The sweetener that Apple hoped would push the deal over the top was that applications written using this API could also be compiled to run on Windows. And so the complete pitch to the Adobes and Microsofts of the world was this: rewrite your huge existing applications using these APIs and end up with a single code base for both Mac and Windows. Alternately, just rewrite the Mac versions of your applications using these new APIs. The answer from the Mac development community was, essentially, "Yeah, uh, no thanks."'