Re: Necromail
Brian Willoughby <[email protected]> Mon, 16 Feb 2009 16:55:03 -0800
| Newsgroups | gmane.comp.web.webobjects.eof |
|---|---|
| Message-ID | <[email protected]> |
So, my next thought is this: Would it be possible to write EOF (and WO) in ObjC as an open-source project? I really have no idea what the current state of affairs is for GNUstep, but I understand they had problems with complex and under- documented classes like NSBrowser. Thus, GNUstep users never seemed to get the full AppKit / Yellow Box / Cocoa experience. I'd hate to see the same lackadaisical situation for EOF, but it would be better than nothing. Perhaps there is a way to create a database adaptor framework for CoreData? Ideas welcome. Bring Back EOF in Objective C !!!! Brian On Feb 16, 2009, at 16:38, Ronald C.F. Antony wrote: On 16 Feb 2009, at 19:16, Brian Willoughby wrote: > Regarding the death of the excellent combination of ObjC and EOF, I > believe we see a victim of the buzz word. Everyone wanted Java on > their web server, so developing in ObjC seemed like a non-feature. > First, a bridge was added to enable Java, then the ObjC side was > ignored. By the time the product made the full transition to Java > - purely to meet the buzz-word requirements - it was less of a > product than it started. > > Personally, I don't think the Bridge alone would be enough. Not if > the core of WO and EOF were continued as Java objects. I would > really like to see a Cocoa+ObjC framework which has the full > capabilities of EOF and WO. Totally agree. And it was a really stupid move, too. Because by the time they did the Java thing, there were plenty of other Java Webapp frameworks, so WO became an "also ran". Meanwhile, ObjC based WO/EOF had something no other framework ever had: a shared data model that could be used for desktop apps, client server apps and web apps, thus eliminating a whole slew of potential problems that happen when the same database is accessed from a variety of clients with ever-so-slightly different models of the data set. Nevermind the ability for code reuse, and what sort of things with iPhone client, EOF server apps would be possible now, you could kiss the Blackberry goodbye in a corporate environment and custom apps. Instead everything is shoehorned into the web metaphor, and it basically sucks all around. Even Apple's stupid web based bug reporting tools is ten times inferior to BugNeXT.app from back in the day. Really stinks that this is what's called "progress". Ronald