Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa superiority?
Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa superiority?
- Subject: Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa superiority?
- From: Deirdre Saoirse Moen <email@hidden>
- Date: Tue, 12 Jun 2001 14:38:52 -0700
Any developer who still thinks it is necessary to write SQL by hand
as a normal part of n-tier app development is wwwaaayyy behind the
times....
I am not convinced (and haven't done any serious testing) that EOF
necessarily creates the most optimized join paths for any given
database. Given that, hand-coded SQL may be a better choice for
performance.
However, that does not mean EOF is an appropriate solution for every
app out there. Specifically, for applications targeted at the
consumer market, it very likely is not appropriate to use EOF as a
solution for persistency. I.e. EOF is not a good replacement for
the traditional multi-document UI that a product like, say,
OmniGraffle, GraphicConverter, or Create. Nor it is appropriate to
apps that are seemingly database centric like, say, iTunes or the
Finder.
There are definitely places where I could argue even for commercial
apps; several of the ones I've written *HAVE* had embedded sql.
Hand-coded, mind you.
Apple is aware that some kind of a generic persistency solution
completely different from EOF needs to be provided to the developer.
Ernie P. repeated this point at several sessions at WWDC.
And we STILL need EOF/ObjC on the client side -- ONLY ObjC.
People forget about in-house database apps.
EOF isn't really appropriate to environments where one is trying to
persist a directed graph of objects where both the graph's
connectivity and the object contents need to be relatively flexible.
Understood, but, for a PIM application (or a shared calendar), that
wouldn't necessarily be the case.
BTW: Stating that the "power of EOF for desktop apps" is not
currently available is inaccurate. Have you actually tried working
with the pure Java EOF in WO 5.x targeted to building Cocoa
applications?
I'll code for windows before I'll code for EOF/Java Client.
Either way, it ain't happening.
Obviously, a remaining issue is one of licensing and it will be
interesting to see how Apple addresses that issue. Let's hope it
is handled with a bit more finesse than some of the licensing events
in past history....
You mean like the clone licensing?
--
_Deirdre Stash-o-Matic:
http://weirdre.com http://deirdre.net
"Cannot run out of time.... Is infinite time. You... are finite....
Zathrus... is finite. This... is wrong tool!" -- Zathrus