4 ms·
OP is lamenting about the Objective-C language verbosity/ceremony compared to Ruby, not the Cocoa Touch framework. After all, you're still using the same iOS f
by danneu 14y ago
OP is lamenting about the Objective-C language verbosity/ceremony compared to Ruby, not the Cocoa Touch framework.
After all, you're still using the same iOS framework with RubyMotion.
But you do get to use Ruby, and more interestingly you get to use rake and Cocoa wrappers like BubbleWrap[1].
[1]: https://github.com/rubymotion/BubbleWrap https://github.com/rubymotion/BubbleWrap
- nirvanatikku 14y agoFair point. I focused a bit too much on the framework itself, but I was really trying to address the 'intimidating' nature of objective-c (as it relates to getting things done in iOS). Certainly I can appreciate the verbosity in comparison and I know where RubyMotion has it's place. Just saying for the folks that are intimidated by objective-c (and have yet to give it a shot): try not to be!
- bora 14y agoMy intimidation doesn't come from the difficulty of Objective-C but 1) The time it takes to build iOS apps using Objective-C and 2) verboseness. I explained above that I think it would take twice as long to build the same app in Objective-C and that thought intimidates me as for most of us the apps we're building are experiments. We don't know if it will catch on or not. And I would like to see results as quickly as possible, especially in a bootstrapped project like this.