I think you'll find that most Cocoa programmers enjoy the Objective-C syntax, mainly because it's very simple and straightforward.
I don't think so. I enjoy the Objective-C semantics. The Lisp-like multiple-bracket syntax is from hell, and only smart editors like TextMate make it really tolerable.
Yes, I think Ruby would be a better language for using a more SmallTalk/ObjC-like syntax:for:method: invocation. But getting rid of the curse of the nested brackets is a worthy tradeoff, and there are massive benefits to Ruby as a language that have nothing to do with the web. Closures (blocks), symbols, the infinitely superior switch (case) statement are some of my favorites. Unification of interface and implementation. No more confounding curlybrackets, and thus no arguments over curlybracket placement. Infinite precision for arithmetic, in addition to the familiar C bitwise operators. Plus, indentation is not significant, and thus you don't have the Pythonian "why am I getting a random syntax error in perfectly legitimate code on line 2661?<...16 hours pass...>Oh, there's a tab instead of some spaces on line 45, and somehow it was OK until I added this new code..."
by Chris — Feb 20
I don't think so. I enjoy the Objective-C semantics. The Lisp-like multiple-bracket syntax is from hell, and only smart editors like TextMate make it really tolerable.
Yes, I think Ruby would be a better language for using a more SmallTalk/ObjC-like syntax:for:method: invocation. But getting rid of the curse of the nested brackets is a worthy tradeoff, and there are massive benefits to Ruby as a language that have nothing to do with the web. Closures (blocks), symbols, the infinitely superior switch (case) statement are some of my favorites. Unification of interface and implementation. No more confounding curlybrackets, and thus no arguments over curlybracket placement. Infinite precision for arithmetic, in addition to the familiar C bitwise operators. Plus, indentation is not significant, and thus you don't have the Pythonian "why am I getting a random syntax error in perfectly legitimate code on line 2661?<...16 hours pass...>Oh, there's a tab instead of some spaces on line 45, and somehow it was OK until I added this new code..."