Re: Cocoa for small applications
Re: Cocoa for small applications
- Subject: Re: Cocoa for small applications
- From: Scott Ellsworth <email@hidden>
- Date: Wed, 14 Sep 2005 11:18:28 -0700
On Sep 14, 2005, at 7:07 AM, Thomas Engelmeier wrote:
At 14:40 Uhr +0100 14.09.2005, Finlay Dobbie wrote:
> >provided at the language layer, and they work like a dream.
Since
>EOF left, Cocoa lacks this support.
So what? Fire up an Java Database layer either by JNI invocation
(some pain) or the Cocoa<->Java bridge (easy, but deprecated).
Yes, but clearly this is painful and a bit of a regression.
For someone who is already fluent in the underlying APIs? Clearly
an "too small userbase to be actively maintained" partial
encapsulation API would be an regression.
A major benefit of Hibernate is how it insulates you from the
underlying datastore. Oracle, MySql, major schema changes, all just
flow by without harm. This is something that a hand-rolled API is
going to have trouble matching, unless a lot of time is poured into
it. For a single developer, it is a marginal case, while for Apple,
it makes a bit more sense - all of their developers would benefit.
I sincerely doubt that the user base would be all that small. At my
clients, at least, Cocoa is a complete non starter for their life
science apps, because they cannot easily get to the databases from
Cocoa.
EOF or Core Data both offer a different abstraction, but one that
fits pretty naturally into the Cocoa design scheme. We already
generate WO models from our schema, so WebObjects app Just Work - I
would do the same with Core Data were it a multi-user access kit.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden