Re: The Problems with NSController
Re: The Problems with NSController
- Subject: Re: The Problems with NSController
- From: Jonathan Wight <email@hidden>
- Date: Sun, 26 Oct 2003 15:20:34 -0600
>
> Experienced programmers know that every line of code is an opportunity
>
> for more bugs, and prefer to minimize the amount of unnecessary code
>
> to accomplish a particular task.
>
>
>
> NSController is very useful for this.
>
>
I'm sorry but that is specious, since writing less code is an attribute
>
of OOP itself, if you use it right. NSController is just another class,
>
which is either written well or written poorly. If the savings in
>
NSController are so magical, I suspect that any good Cocoa developer
>
has already abstracted similar functionality. Apple does not have a
>
monopoly on software engineering principles, whether they built the OS
>
or no.
It's not magical. Interface Builder is effectively doing more of the work
for you. Just like how Interface Builder removes some of the tedious parts
of UI creation it also is now capable of removing some of the tedious parts
of UI logic too.
>
What you are really saying is that it saves lazy programmers the work
>
of doing their own software engineering. Just think how much coding I
>
would not have to do if I were not a programmer at all!
You can use the same argument against any vendor supplied API. Heck - _real_
programmers code in machine code anyway, everyone else is just lazy! ;-)
Jon.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.