I think for standard Cocoa desktop development, ObjC 2.0 offers the best of both worlds. A well-formated Cocoa project with useful method naming in Objective C reads almost like prose, especially with all the noise of memory management and stuff like explicitly setting up NSEnumerators gone. A random line of code I was just looking over:
...
if (![[[[NSWorkspace sharedWorkspace] launchedApplications]\
valueForKey:@"NSApplicationBundleIdentifier"]\
containsObject:externalEditorBundleIdentifier])
...
Sure, the use of brackets is a bit excessive, but this is basically a sentence. If you can read English, you know what this is supposed to do. It may be verbose, but if you are actually typing out more than 10% of this line, you need to get a better editor instead of complaining about the syntax. In my book, code readability is far, far more important then "writability".
PyObjC and RubyCocoa have both been around for a long time. RubyCocoa has recently seen a lot of improvements (both in speed and features) because of the efforts of one Apple developer. These changes are significant, but not significant enough to say that Cocoa is now "gaining built-in Ruby support". You have been able to write Cocoa apps in Ruby or Python for years.
Of course it has been possible, but it was not exactly officially endorsed by Apple. If thinks break going from one version to the next, its now technically Apple's bug. I think that's quite a big difference.
by Michael Stroeck — Feb 20
... if (![[[[NSWorkspace sharedWorkspace] launchedApplications]\ valueForKey:@"NSApplicationBundleIdentifier"]\ containsObject:externalEditorBundleIdentifier]) ...Sure, the use of brackets is a bit excessive, but this is basically a sentence. If you can read English, you know what this is supposed to do. It may be verbose, but if you are actually typing out more than 10% of this line, you need to get a better editor instead of complaining about the syntax. In my book, code readability is far, far more important then "writability".
PyObjC and RubyCocoa have both been around for a long time. RubyCocoa has recently seen a lot of improvements (both in speed and features) because of the efforts of one Apple developer. These changes are significant, but not significant enough to say that Cocoa is now "gaining built-in Ruby support". You have been able to write Cocoa apps in Ruby or Python for years.
Of course it has been possible, but it was not exactly officially endorsed by Apple. If thinks break going from one version to the next, its now technically Apple's bug. I think that's quite a big difference.