I've not used RubyMotion despite coming from a Ruby background because it looks like you wind up writing a lot of Ruby that ends up looking an awful lot like, well, Objective C. It doesn't feel very much like Ruby. If the code is just (or nearly) as verbose and obscure, why bother giving up Xcode, storyboards, etc and adding a dependency on RubyMotion?
I feel like the hurdles of learning Cocoa are far greater than those of Objective C, and potentially even tricker because you've got to translate it into Ruby.
But I acknowledge this concern is not born of experience. Anyone care to comment?
I feel like the hurdles of learning Cocoa are far greater than those of Objective C, and potentially even tricker because you've got to translate it into Ruby.
But I acknowledge this concern is not born of experience. Anyone care to comment?