On Mar 28, 2011, at 11:07 AM, Nathan Sims wrote: > > On Mar 27, 2011, at 12:36 PM, Michael_google gmail_Gersten wrote: > >> Maybe part of the issue is which WebObjects. Originally, WO and EOF >> were Objective C; java was supported by a bridge. Then, everything >> became Java, first, and objective C was supported by a bridge. Now, >> that bridge (as I understand it) is gone, and Apple is just doing >> generic Java. > > No one has ever been able to give me a convincing answer as to why EOF was > ditched in favor of CoreData. I can understand EOF, it feels object-oriented > and ObjC-like. CoreData is a like a plate of spaghetti to my mind, very C++ > like, syntaxy, and hard to get your head around ...
It has been a while since I did EOF (ObjC) but Core Data reminds me a lot of EOF. (Not that I have a ton of CD experience -- one simple Mac app and one iPhone app I am currently working on -- but in both cases it took me almost no time to implement what I wanted to do in CD). EOF was ditched because it required a special database adapter for each database and Apple had a hard time getting the database developers to cooperate and it was too much to keep track of and do themselves. Remember, Apple was in different circumstances when EOF was ditched (ObjC). Additionally, with the move of WebObjects to Java, EOF became implemented in Java and there was no pressing need to commit development resources towards it. With CD, there is only SQLite and the flat file formats to worry about._______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
