[MacRuby-devel] OS X10.9 & MacRuby's future...

[Mark Villacampa]

IMHO MacRuby and now Rubymotion apps deployment is really reasy. To create a release version of a .app in RubyMotion you just "rake release" and you're done.

For cross-platform development with Qt, Tk or wx, the situation in Python has always been better than in Ruby. I don't know how we'll maintained the ruby bindings for each of those GUI toolkits are, but packaging and deployment of such apps has always been a pain even in Python. I don't know if a toolkit-indepented ruby2app library would be the solution. Too many differences between them. If only each of the bindings had nice a packing workflow for each OS... 

On Thursday, May 16, 2013 at 11:32 PM, Kevin Walzer wrote:

> On 5/16/13 2:38 PM, Mark Villacampa wrote:
> > 
> > The momentum around MacRuby has been inexistent for almost a year and a
> > half. That is, since Laurent Sansonetti (the original creator of
> > MacRuby) left Apple, and that left the project without maintainers who
> > were being paid to work on it. Only Watson and a couple other
> > maintainers have been doing maintenance work and fixing a couple of bugs.
> > 
> > Since nobody is being paid to maintain it, and (AFAIK) there is no
> > company/individual whose main/critical systems depended on MacRuby,
> > nobody has taken over the project. This is pretty much a chicken-egg
> > situation.
> > 
> 
> 
> It's unfortunate that MacRuby is suffering from bit-rot, but it was not 
> an optimal solution for desktop development in any event. It was 
> incompatible with standard Ruby in subtle ways, and was an incomplete 
> implementation.
> 
> Standard Ruby has nice bindings to several UI toolkits (Qt, Tk, wx) and 
> can access Cocoa API's via Tim Burks' under-documented rubyobjc module, 
> but it too has problems for desktop apps. Everything kind of falls apart 
> when you look for available deployment tools outside of those that are 
> tightly bound to RubyCocoa or MacRuby (i.e. standaloneify).
> 
> It would be really great if someone could put together ruby2app (Ruby 
> version of py2app) in a way that would work with any Ruby libraries, not 
> just Cocoa ones. But I'm not going to hold my breath.
> 
> --Kevin
> 
> -- 
> Kevin Walzer
> Code by Kevin/Mobile Code by Kevin
> http://www.codebykevin.com
> http://www.wtmobilesoftware.com
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org (mailto:MacRuby-devel at lists.macosforge.org)
> https://lists.macosforge.org/mailman/listinfo/macruby-devel
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20130516/34194917/attachment.html>