RubyMotion - Ruby for iOS
rubymotion.com
RubyMotion - Ruby for iOS
1–10 of 250 posts
Re: RubyMotion - Ruby for iOS
#2This looks really cool -- would be nice if there was some way to try it out before buying.
Re: RubyMotion - Ruby for iOS
#3This is from Laurent Sansonetti, the original author and long time maintainer of MacRuby. It doesn't say that anywhere until after you buy it, which they should really change since that made me go from "Uh, did some random guys just take MacRuby's code and hack in some extra stuff to sell it?" to "Holy crap so THIS is what he's been working on!"
Re: RubyMotion - Ruby for iOS
#4This is really awesome, but I found some bad news in the FAQ:
> Because RubyMotion implements a dialect of Ruby that is statically compiled, regular Ruby gems will not work in RubyMotion. We provide documentation which describes how to architect gems to work with RubyMotion.
Re: RubyMotion - Ruby for iOS
#5nice, but where is the advantage over just using objc? the hard part of coding for iOS isn't objc, it's learning how to use all the API's.
Re: RubyMotion - Ruby for iOS
#6This is from Laurent Sansonetti, the original author and long time maintainer of MacRuby. It doesn't say that anywhere until after you buy it, which they should really change since that made me go from "Uh, did some random guys just take MacRuby's code and hack in some extra stuff to sell it?" to "Holy crap so THIS is what he's been working on!"
Actually they say that this is based on MacRuby:
http://www.rubymotion.com/features/
at the bottom of the page:
RubyMotion is based on MacRuby, a widely-used implementation of Ruby created and maintained by Apple for over 4 years. Starting from a solid and stable code base, the guys who originally created MacRuby now work on RubyMotion. You're in good hands.
Re: RubyMotion - Ruby for iOS
#7nice, but where is the advantage over just using objc? the hard part of coding for iOS isn't objc, it's learning how to use all the API's.
Having been part of the private beta I can tell you that it's a huge time saver. Objective-C is nice be ruby is much more expressive, you can use the same API with much less code, you can skip XCode altogether and use your favorite editor, ...
I can't express properly how awesome it is, really.
Re: RubyMotion - Ruby for iOS
#8This is from Laurent Sansonetti, the original author and long time maintainer of MacRuby. It doesn't say that anywhere until after you buy it, which they should really change since that made me go from "Uh, did some random guys just take MacRuby's code and hack in some extra stuff to sell it?" to "Holy crap so THIS is what he's been working on!"
Actually they say that this is based on MacRuby: http://www.rubymotion.com/features/ at the bottom of the page: RubyMotion is based on MacRuby, a widely-used implementation of Ruby created and maintained by Apple for over 4 years. Starting from a solid and stable code base, the guys who originally created MacRuby now work on RubyMotion. You're in good hands.
Ah, now I see! I suppose I glossed over that. It should be bigger. ;)
Re: RubyMotion - Ruby for iOS
#9nice, but where is the advantage over just using objc? the hard part of coding for iOS isn't objc, it's learning how to use all the API's.
It depends, if your background is in dynamic languages like Perl, Ruby, Python than using Ruby for iOS makes a lot of sense. On the plus side Ruby is better for programmer productivity.
If you have a good background in C than yes, using Objective-C is not so difficult.
Re: RubyMotion - Ruby for iOS
#10I could see this really taking off.
My worry is that it would take off so well that the ruby gem community could get fragmented into libraries for RubyMotion and libraries for regular ruby projects.