InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

JRuby 1.2 RC1 Released, Initial support for Android

Posted by Werner Schuster on Feb 25, 2009

Sections
Development,
Architecture & Design
Topics
Java ,
Ruby ,
JRuby ,
Runtimes ,
Mobile
Tags
Virtual Machines ,
Ruby1.9 ,
Android ,
JRuby

JRuby 1.2 RC1 has been released (JRuby 1.2 RC1 Download). JRuby 1.2 is a maintenance release, but it marks the switch to a slightly different versioning scheme, ie. future maintenance releases will change the x in 1.x.
JRuby 1.2 contains a large number of bug fixes, result of a major cleanup of the JRuby JIRA bug database.

The release also comes with improvements to compatibility with both Ruby 1.8 and Ruby 1.9, from the release notes:

- Improved Ruby 1.9 support (via --1.9)
  - Compiler now works
  - Almost all of the missing 1.9 methods have been added

The performance has also been improved in many areas, again from the release notes:

- New experimental --fast flag which does more aggressive optimizations
- Large scale compiler and runtime cleanup and performance audit
- Parsing is 3-6x faster now.


The 1.2 release also contains the beginnings of a long awaited feature: JRuby on Android. Some of the changes can be seen in a commit, which fixes some compatibility issues.
The Android support also seems to use only JRuby interpretation and not JIT compilation (compilation of Ruby source to Java bytecodes), as can be seen by the command shown on Charles Nutter's blog, where he uses this to run JRuby on Android:

dalvikvm -classpath ruboto.jar org.jruby.Main -X-C test.rb

The "-X-C" flag turns off JRuby's JIT compilation.

The availability of JRuby on Android might help change the situation of Ruby on mobile devices. Rhodes is a Ruby-based framework which already brings Ruby to the iPhone, Symbian and Windows Mobile, as well as to Java-based devices like the Blackberry, with Android support planned for one of the next releases.

Finally, the current JRuby release is the first release candidate for the 1.2 release - this means, now is the time to report regressions or problems that should be fixed for the final 1.2 release.

MRI by Roger Pack Posted
  1. Back to top

    MRI

    by Roger Pack

    appears you can run MRI on it, too
    otype.net/2009/01/static-ruby-miniruby-187-on-a...
    blog.xwings.net/?p=112
    for what it's worth

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.