On Friday, April 6, 2012 at 8:00 PM, Henry Maddocks wrote:
> I have Ruby, C, C++ and Obj-C experience, but the one thing that is holding
> me up from contributing is a simple one page description from the source
> level of what happens when you run a script in MacRuby. Is anyone able to
> write one?
I gave a talk last year to Boston.rb that they graciously taped and put online.
You can find it here:
http://bostonrb.org/presentations/macruby-what-is-it-and-why-should-i-care-part-1
. Hopefully it should answer most of your questions around how MacRuby works.
If not, hit me up on IRC! :-)
> I'm not sure the world needs another ruby VM. With Evan Pheonix's involvement
> is now the time to investigate merging the Rubinius and MacRuby VMs or are
> they too different? Can MacRuby leverage the work of the Rubinius team in
> some way?
>
>
>
The MacRuby VM is very nicely tailored to the job of running on top of the
Objective-C runtime. It is also fairly mature. Personally, I see no technical
reason that a proliferation of VMs should be a problem (there are at least 3
major Java VMs…4 if you disregard Oracle's lawyers and count Dalvik).
> With the death of Obj-C GC why isn't MacRuby being ported to use ARC or even
> retain/release? Why does it need it's own memory handling scheme?
>
>
>
I would assert that Ruby without automatic memory management can hardly be
called Ruby. ARC is a compile-time tool, so using it directly is not an option.
Whether we call memory management a garbage collector or an automated reference
counter is, I think, a matter of semantics. However, memory needs to be managed
"somehow".
- Josh
_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
