The point of my email was:
Use RVM to install 1.9.2 or jRuby or whatever.
Install MacRuby from source or the package, and execute it using `macruby`,
`macirb`, and the like. There is no reason to overload `ruby` to point at
macruby, which is the only real benefit RVM gets you.
On Fri, May 20, 20
Not true.
For those of us that have a lot of gems, being able to use gemsets with MacRuby
can yield significant speed ups when loading something that requires a gem.
As a quick benchmark I chose to load the "abstract" gem because it is a single
file weighing in at 75 lines (including comments
This is a problem with MacRuby, not Rubygems
On Sat, May 21, 2011 at 11:38 PM, Mark Rada wrote:
> Not true.
>
> For those of us that have a lot of gems, being able to use gemsets with
> MacRuby can yield significant speed ups when loading something that requires
> a gem.
>
> As a quick benchmark
The topic is rvm with MacRuby, so it is a relevant point. And the problem is
not just MacRuby, but both are being actively developed right now so the point
is kind of moot.
Mark Rada
mr...@marketcircle.com
On 2011-05-21, at 11:42 PM, Chris Rhoden wrote:
> This is a problem with MacRuby, not