Design Element
Comment on "Apple's Overall Strategy for Frameworks"
by Karl Gretton — Dec 14
I concur with the last comment from Andrew L. Having use WO both in its Obj-C days and in more recent times, WO was held back by many issues that existed in the underlying Apple frameworks.

It seems that Obj-C is ideally suited to desktop applications. As anyone reading this post knows, amazing applications can be created with very little code - compared with the mess that the typical M$ Visual Studio application generates or Eclipse/Java. However, it never seemed to scale for WO.

EOF had many performance issues around multi-threading, concurrent request handling, faulting issues within its various layers (EOAccess, EODatabaseContext, etc). Following the 'auto-port' (Apple just basically put their EOF code through the sausage grinder Obj-C to Java conversion utility), most of these issues have been thoroughly addressed and WO now runs beautifully in Java - much better, in my view, than it ever did with Obj-C.

And Andrew is right. As soon as a new OS, DB or anything else arrives on the scene, we have the necessary drivers to use it, rather than waiting for an Apple release cycle.

So Java for the server side and Obj-C for the desktop.
Back to "Apple's Overall Strategy for Frameworks"
Design Element

Copyright © Scott Stevenson 2004-2015