MRI (Matz’s Ruby Interpreter)
As I mentioned earlier, this is the default Ruby implementation, written by the creator team lead by Yukihiro Matsumoto. By default I mean, if a vendor by chance includes a version of Ruby as a part of software initially installed on the operating system, then MRI will be the implementation. This implementation gets sponsored by the core team, as well as other contributors who would like to see Ruby grow. Every Christmas, the developers release an update to MRI, often including some new language features.
This implementation has potential to gain popularity among the developers. It is a version of Ruby, which is implemented on top of JVM (Java Virtual Machine). This gives Ruby an opportunity to become yet another language that runs on JVM, except for Java. In this scenario, Ruby runs everywhere where Java would run. The implementation has its advantages, but it also lacks some of the features that Ruby has, which means it can only be perfect for certain projects, but not all possible scenarios. Some developers admit that switching to JRuby increased the performance of their applications.
This implementation of Ruby represents its embeddable version. With this implementation, you can apply Ruby as a scripting language, and even use it to program microcontroller boards. The other uses of mruby include building of iOS apps, embedding mruby into iOS apps to increase their performance, and giving users the access to an embedded scripting language. The variety of the devices with operational system is very broad today, and mruby promises to solve the problem by increasing performance multi-platform.