3 ms·

He spoke about Object Oriented Programming as a paradigm, but many times he referred to WebObjects, an OOP web framework that NeXT developed. Interesingly, Appl

by M4v3R 12y ago

He spoke about Object Oriented Programming as a paradigm, but many times he referred to WebObjects, an OOP web framework that NeXT developed. Interesingly, Apple Store and other Apple websites still use this tech.

leoc 12y ago
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."'
coldcode 12y ago
I started with WO on NeXT in 1998, it was a amazing way to build web applications (in the pre-JS days). There are still WO apps in use today. The biggest benefit was Enterprise Objects, which Core Data is based on today on iOS, which made messing with big databases pretty easy. It was written in Objective-C at the time which was pretty oddball, but at Apple it eventually moved to Java and then become less supported as Apple clearly had other priorities. But WO was a lot of fun to work with even on large projects.
dzhiurgis 12y ago
The way he pushes WebObjects sounds like yet another API standard. We keep chasing this integration/communication/data interchange unicorn to todays date.

by M4v3R 12y ago

leoc 12y ago

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."'

coldcode 12y ago

I started with WO on NeXT in 1998, it was a amazing way to build web applications (in the pre-JS days). There are still WO apps in use today. The biggest benefit was Enterprise Objects, which Core Data is based on today on iOS, which made messing with big databases pretty easy. It was written in Objective-C at the time which was pretty oddball, but at Apple it eventually moved to Java and then become less supported as Apple clearly had other priorities. But WO was a lot of fun to work with even on large projects.

dzhiurgis 12y ago

The way he pushes WebObjects sounds like yet another API standard. We keep chasing this integration/communication/data interchange unicorn to todays date.