Well, no, it neither floats nor carries planes. HOWEVER ...
With Core Data, there are a lot more messages being sent through
several more layers. For simpler data models, it's inevitable that
there'd be more messages being sent (valueForKey, etc). For a simple,
flat list (take a very basic "Notes" app for example, that has only
"noteDescription" and "completed"). With Bindings, a lot of messages
are going back and forth to keep the model in sync with the UI. But
what about behind the scenes? With Core Data, you're loading a model,
then asking the managed object context and the persistent store
coordinator to get every one of these objects to display their only
two properties in a table anyway.
Clearly more actual obj-c messages are being sent around to do all
that than would be sent to simply read in an array of dict objects
from a file and hand it to an array controller.
If you refer to my previous message, I *did* say that my comments
weren't to imply that Core Data was any kind of slow beast (in fact,
I'm in awe of its power and simplicity), but the fact is, it *is*
more resource intensive than initWithContentsOfFile: in at least
*some* cases. :-)
On Jul 28, 2005, at 12:21 PM, Charilaos Skiadas wrote:
Is CD really that heavy? (And can it really float on water and
carry planes ? :-) )
I was always under the impression that it was relatively light, and
for me anything that minimizes the amount of code I have to write
is good. Sure, if it is just a dictionary or just an array, no
reason to use CD, but if the data is even slightly bit complicated,
is there really an overhead, especially compared to the bugs an
average programmer (myself included) could introduce to produce the
same effect?
In particular, how does the overhead compare to using vs not using
bindings?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
