Re: Newbie Help understanding Core Data
Re: Newbie Help understanding Core Data
- Subject: Re: Newbie Help understanding Core Data
- From: Charilaos Skiadas <email@hidden>
- Date: Thu, 28 Jul 2005 11:21:32 -0500
On Jul 28, 2005, at 7:46 AM, SA Dev wrote:
On Jul 27, 2005, at 4:56 PM, Charilaos Skiadas wrote:
In sort, I see no reason for any application that handles a lot of
data to not use Core Data for that.
Actually, there are plenty of reasons. :-)
And all very good reasons indeed :-)
I'm afraid I was talking from the perspective of a hobbyist
programmer just playing around with the frameworks, which I guess is
what I do. As you point out, there are a number of reasons for an
"industrial strength application" to not use CD. So my comment above
was a bit hasty in retrospect.
4 - K.I.S.S. ("keep-it-simple-stupid") Principle - Using Core Data
for something ultra simple (like a simple list of items with one or
two properties each) is like swatting a fly with an aircraft
carrier.*** When a simple dictionary or array's read/write to/from
file methods will work just fine, Core Data is a bit much, even if
that list is several thousand lines long, if it's just a few
properties that are all listed in a flat table, their values are
going to be retrieved anyway ...
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?
Haris
_______________________________________________
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