natively in the objective c runtime Rubymotion has a number of internal differences which allow it to run within the sandboxed iOS Including memory management code as iOS lacks proper garbage collection
community. Concerns about what long term support So far so good, lots of regular updates and good customer support About the same cost as the iOS Developer Program
# RubyMotion def pickerView(pickerView, titleForRow:row, forComponent:component) ... end Code The are quite similar, syntactic sugar aside, except for the static typing The main difference between Rubymotion and normal ruby motions are the keyword arguments
on the command line using rake Debugging is done with the rubymotion repl, which integrates with the iOS simulator A debugger was released a few weeks ago
cases Right now it feels risky to invest a lot of time and money into building a large, complex rubymotion app That being said, we have started building a number of medium size apps within Forward that we plan on putting in the App Store