As we near v1.0, the picture is getting clearer as to what will and won't make the cut. I'd like to talk about some of the more technical decisions made along the way, such as why MacRuby has its own GC, Regular Expression engine, and how we are utilizing Ruby 1.9's new symbol-key hash syntax to make integration with Cocoa and other Obj-C libraries as smooth as possible. Finally,...
[read more]
As we near v1.0, the picture is getting clearer as to what will and won't make the cut. I'd like to talk about some of the more technical decisions made along the way, such as why MacRuby has its own GC, Regular Expression engine, and how we are utilizing Ruby 1.9's new symbol-key hash syntax to make integration with Cocoa and other Obj-C libraries as smooth as possible. Finally, implementing Ruby provides some unique insights into what features of the Ruby language make it hard to go faster. This should also provide a starting point to discuss what compromises could be made in the future to make sure Ruby remains relevant in a world of fast JS interpreters, Lua JIT, Python 3, and others.