Re: ADC Core Data article
Re: ADC Core Data article
- Subject: Re: ADC Core Data article
- From: Todd Blanchard <email@hidden>
- Date: Sat, 9 Apr 2005 23:32:25 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think they deserve the benefit of the doubt.
Ya do, do ya? Based on the far from stellar product stewardship of the
WebObjects/EOF product line, I don't.
Reading the article, it looks like warmed over EOF but without any
adaptors for real databases. There's nothing about the modeling tool,
but I'll wager that they've done away with the part where you design
the tables as well as the entities and then supply mappings. I'll
suspect (with no real info as I'm not paying money to ADC to support my
hobby) that you just design the entities and it does naive entity to
table mapping in the SQLite adaptor.
Which does absolutely nothing for people who already have databases
that want to build interfaces. I also have to wonder about multi-user
support. If you're going to do small business apps, you need
multi-user. EOF had optimistic locking. I suspect, given the focus on
desktop apps, that this is absent and will need to be written. I also
wonder if its open enough to allow someone to develop a good adaptor to
PostgreSQL or Oracle.
Even though we're only discussing public information at this point, I
think it's an interesting study on why Apple goes to such extents to
hold things close to the chest until the thing actually ships.
You mean so they can continue to feel good about ignoring their
developers every year while working to release apis that don't meet our
needs?
- -Todd Blanchard
On Apr 9, 2005, at 4:58 PM, Scott Stevenson wrote:
On Apr 9, 2005, at 3:16 PM, Marcel Weiher wrote:
Take home message: CoreData controls how things are stored in those
XML/SQLite files, and this may change at any time. So you don't own
your data format, if you use CoreData persistence.
Nope. NSCoding is a protocol, it will work with any style
archiver/unarchiver you choose to implement. For example, I use my
own MPWXmlCoder, which works just fine with both Apple internal and
my own classes via NSCoding. It also works fine under GNUStep...
I'm afraid you're missing some crucial bits of information here, and
scaring people away from Core Data before Tiger is even out. This is
unfortunate because Core Data is really well designed. I think they
deserve the benefit of the doubt.
Even though we're only discussing public information at this point, I
think it's an interesting study on why Apple goes to such extents to
hold things close to the chest until the thing actually ships.
- Scott
--
http://treehouseideas.com/
http://theocacao.com/ [blog]
_______________________________________________
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFCWMh5hullemWJdQ8RAphAAJ9hNdHetc9I4aw0GLVZdX+euoqMkgCg09T3
r5NLDaWp4z91tekYGjdqdd4=
=JJCt
-----END PGP SIGNATURE-----
_______________________________________________
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