4 ms·
There is still a lot that you can do to contribute back to the project. Much of the build system and various supporting libraries have been open-sourced. Furthe
by jballanc 14y ago
There is still a lot that you can do to contribute back to the project. Much of the build system and various supporting libraries have been open-sourced. Furthermore, it is the stated goal of RubyMotion that development of higher-level abstraction libraries should be driven by the community.
I suspect that the number of people who would actually be interested in (or, indeed, even capable of) contributing back to the parts of RubyMotion that are closed source is rather small.
- DigitalJack 14y agoProbably true. But as an amateur developer, I'd like to try it out... yet I'm not in a spot where I can just drop $200 to see if I like something or not. How similar is MacRuby?
- evilduck 14y agoBesides the obvious difference of target platforms, the biggest difference you'll run into IMO is that MacRuby is a full Ruby 1.9 implementation on top of Objective-C, whereas RubyMotion is more of a dialect of Ruby. i.e. eval doesn't exist in RubyMotion, you can't require gems at runtime, can't use MiniTest or RSpec, etc.