Ruby Weekly is a weekly newsletter covering the latest Ruby and Rails news.

Is It Ruby 1.9: Report and Track How Compatible Ruby Libraries Are With 1.9

By Peter Cooper / February 6, 2009


Ruby 1.9.1 was released last week but due to the significant changes between the 1.8 and 1.9 versions of MRI, not all libraries and gems work with it. The trouble is.. which do and which don't? My advice last week was to just start playing and not to switch anything serious across until you could guarantee all of your preferred libraries worked.

Is It Ruby 1.9 - developed by Rails host Brightbox - helps with the process of tracking gem compatibility with Ruby 1.9. It's a place for the Ruby community to both report and track compatibility for all public gems. For example, I can see that so far 3 people have reported success with Hpricot and 2 have reported failures. If you visit the Hpricot specific page, you can read the reports users have given to find out how to get it working on 1.9.1. The same applies for every other gem..

This is a great resource and if you're savvy enough to play with 1.9.1 and to try installing gems, get on to Is It Ruby 1.9 now and report your own results. A lot of gems have no reported failures or successes yet, so there's a lot of opportunity to help the community out. Alternatively, if you just want to get help and monitor progress, you can also subscribe to RSS feeds for the gems you're most interested in.

Disclaimer: Brightbox is a Ruby Inside sponsor, though this post is not connected to that :)


  1. MarquisDeBad says:

    Sorry, this is a waste of time.

    Take Hpricot. 5 comments on 3 versions on 3 or maybe 4 setups. 3 marked as working - except one of those actually states in the comment it's failing - and 2 marked as failing. Apparently something's been fixed, apparently it hasn't been fixed, and - oh - and good luck tracking progress cos there aren't any dates.

    So is Hpricot ready for Ruby 1.9? I am none the wiser.

    Would the lighthouse/official mailing list/support forums be a better focus of this energy? Definitely.

  2. Peter Cooper says:

    It does show that someone installed the 0.9.x version from Github successfully on 1.9.1, so I consider that useful. I've also learned that the inability to build is something to do with fast_xs and that there is progress on that being fixed.

    This isn't a "find out how to install every gem on 1.9.1 right now" type thing.. it's a share knowledge, check out what's going on, and hopefully we can figure it out sort of thing.

  3. Steve Murbach says:

    I am not sure I get the whole point of releasing Ruby 1.9 at this stage. Why should they say that this latest release is STABLE and then come back to tell us that many of the libraries and gems do not work with it? Is that the kind of frustration and lack of common sense we should to be offering to the Ruby community if we claim that Ruby is a "great and very-much-at-ease" language that it is meant to be? Now I am not in a position to proudly show off Ruby's latest realese to other developers.

  4. Peter Cooper says:

    Steve: It's a chicken and egg situation. If a release of 1.9 hadn't gone stable then library developers wouldn't bother developing against it. So.. it takes a slightly shaky stable in order to get people to actually start using it.

    Ruby 1.9 has been around in some form or another for well over a year now yet the libraries are STILL not done for it.. so just keeping things in development mode does not work whatsoever for encouraging people to bring their code up to standard :(

Other Posts to Enjoy

Twitter Mentions