First, RubyCocoa has a new messaging syntax as part of the 1.0 preview. For information about it, check out What's New in RubyCocoa's 1.0 sneak preview. Here is a before and after with your example code:
Second, why are you (and all the other Mac bloggers) talking like these bridges are something new?
I'm thrilled that Cocoa is gaining built-in Ruby and Python support, particularly because it lowers the barrier to entry.
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.
by Ryan Brown — Feb 19
First, RubyCocoa has a new messaging syntax as part of the 1.0 preview. For information about it, check out What's New in RubyCocoa's 1.0 sneak preview. Here is a before and after with your example code:
Before:
@timer = OSX::NSTimer.scheduledTimerWithTimeInterval_\ target_selector_userInfo_repeats(\ 1.0/60.0, self, :tick, nil, true)After:
OSX::NSTimer.objc_send(:scheduledTimerWithTimeInterval, 1.0/60.0, :target, self, selector, tick, :userInfo, nil, :repeats, YES);Second, why are you (and all the other Mac bloggers) talking like these bridges are something new?
I'm thrilled that Cocoa is gaining built-in Ruby and Python support, particularly because it lowers the barrier to entry.
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.