4 ms·
That's not necessarily a bad thing: if you're like me (seasoned Objective-C developer, and only the briefest exposure to Ruby) it's quite informative. A lot of
by objclxt 14y ago
That's not necessarily a bad thing: if you're like me (seasoned Objective-C developer, and only the briefest exposure to Ruby) it's quite informative.
A lot of talk about RubyMotion has been about how Ruby developers and those who aren't familiar or comfortable with Objective-C can develop for iOS. I don't see why it can't work in the other direction as well: a nice entry point for people familiar with Objective-C looking for an easy-in for Ruby.
- barumrho 14y agoSure, that could be a pro of RubyMotion, but then that's not the goal. I develop in Objective-C as well, and I am very interested in what RubyMotion will bring to the table. So far, what I've seen is typical Objective-C code translated to Ruby. That doesn't offer me any advantage. What I want to see is something that will significantly boost productivity. REPL seems like one of them, but I want to see something on the code level.
- jcromartie 14y agoUnfortunately, it seems like those who aren't familiar or comfortable with iOS and Objective-C will still be completely lost with RubyMotion.
- sirn 14y agoI don't think diving into RubyMotion without knowing iOS API is that overwhelming; my only first hand experience with Objective-C was when I tried to submit a very small patch (2 lines) to open source project, yet I still found RubyMotion to be very easy to work with. There are few things I wish it was simpler (e.g. Core Data) but I guess this will be fixed over time with RubyMotion wrappers and some kind of DSL.