Okay, fair enough. How about other resources? Memory, for
instance? :-) A small, quick little app shouldn't have to create
extra objects (the Core Data structure) *in addition to* sending
extra messages through unneeded layers. It's still good housekeeping.
Drop in the bucket sort of thing; one or two are only acceptable if
the bucket's not already full to the brim. A quick and dirty little
utility app should contribute as little as possible to that bucket.
But then, I'm not expert at resource management (my early apps
leaked like the Titanic and my latest still have enough trickles to
frustrate me).
Anyway, that's why I listed "K.I.S.S." as my last reason (but if
it's in order of importance, than backward compatibility should be
first in my opinion). But it's a reason nonetheless. :-)
On Jul 28, 2005, at 3:36 PM, Hamish Allan wrote:
I've only really been following this exchange in passing, so
forgive me if this is a daft thing to say. But for the simple case,
does the extra overhead not matter less anyway? If your "Notes" app
is only serialising two pieces of information, your user isn't
going to notice that ten extra messages (or whatever) needed to be
sent, it's going to be near-enough instantaneous anyway. Cue
premature optimisation debate ;)
_______________________________________________
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
