Linked by Thom Holwerda on Mon 2nd Jun 2008 09:36 UTC
Permalink for comment 316731
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2007-04-18
The problem here is that you are putting Objective-C/Cocoa into the same league in terms of programming complexity as C/C++, whereas in reality it is much more similar to Java/C#. 99% of the time you don't really have to deal with pointers (one can regard 'ClassName *var;' as syntax sugar, so that doesn't really qualify as pointer manipulation) and Objective-C's strong dynamic mechanisms work very well for GUI environments, which are by nature hard to describe flexibly using static typing. This is further emphasized in ObjC-2.0 which features an automatic GC.
As the author pointed out, no single feature of Objective-C or Cocoa really put them above other players. It's much more about the combination and implementation of these features. Also, one can transition programming styles from dynamic RAD with good code manageability all the way down to assembly-level programming without having to switch languages.