This is probably one of the better articles on RubyMotion: mainly in that it's fairly balanced...it annoys me to see posts like "Why Ruby Motion is Better than

This is probably one of the better articles on RubyMotion: mainly in that it's fairly balanced...it annoys me to see posts like "Why Ruby Motion is Better than Objective-C", or "Ruby Motion: The Worst Thing to Happen to iOS"... As an Objective-C developer who knows very little Ruby, this probably isn't for me. But I can't see how opening up iOS to a wider range of developers is a bad thing: personally, I'm an Objective-C fan, but I can see why people don't like it, and if you're at a start-up or a small team looking to get some app deployed and you don't want the hassle of learning Objective-C then this seems like a great alternative. So like any language or environment there are pros (the REPL looks amazing) and cons (closed source, at least in my view). And whilst I'm sure this wasn't the intention of RubyMotion at all it's actually making me revisit Ruby as an Objective-C developer and see if I can improve my knowledge and experience of it. No bad thing!