The Broken Promises of MRI/REE/YARV
timetobleed.com
The Broken Promises of MRI/REE/YARV
1–10 of 75 posts
Re: The Broken Promises of MRI/REE/YARV
#2[deleted]
Re: The Broken Promises of MRI/REE/YARV
#3[deleted]
The article covers it but those are different C-based Ruby VM implementations:
- 1.8 is MRI
- 1.9 is YARV
- 1.8 plus performance patches is REE
Re: The Broken Promises of MRI/REE/YARV
#4[deleted]
MRI = Matz's Ruby Interpreter = Ruby 1.8
YARV = Yet Another Ruby VM = Ruby 1.9
REE = Ruby Enterprise Edition = Ruby 1.8 with a modified garbage collection system to make it friendly to vforking.
These are all versions of ruby written in C.
Re: The Broken Promises of MRI/REE/YARV
#5[deleted]
They're Ruby interpreters -- Matz's Ruby Interpreter, Ruby Enterprise Edition, and Yet Another Ruby VM respectively.
Re: The Broken Promises of MRI/REE/YARV
#6[deleted]
[deleted]
Re: The Broken Promises of MRI/REE/YARV
#7Re: The Broken Promises of MRI/REE/YARV
#8[deleted]
Ruby virtual machines. MRI is the VM for ruby 1.8 (Matz ruby implementation and Matz is the creator of ruby), YARV is the newer incanation that was developed for ruby 1.9 these are all written in C. There plenty of other ruby VMs like rubinius or jruby etc.
Re: The Broken Promises of MRI/REE/YARV
#9[deleted]
MRI - Matz' Ruby Interpreter (the default Ruby)
REE - Ruby Enterprise Edition (unofficial branch of Ruby 1.8)
YARV - Yet Another Ruby VM (the VM used in Ruby 1.8)
(Although in this case I think he means MRI = 1.8 and YARV = 1.9)
Re: The Broken Promises of MRI/REE/YARV
#10[deleted]
[deleted]