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.

Ruby VM Roundup: Ruby 1.9.1 Preview 1, Rubinius Moves To C++ VM

Posted by Werner Schuster on Oct 28, 2008

Sections
Development,
Architecture & Design
Topics
Ruby ,
Language Design ,
Language ,
Runtimes ,
Dynamic Languages
Tags
Ruby1.9 ,
Virtual Machines ,
C++ ,
Rubinius

Ruby 1.9.1 Preview 1 has been released (Download site). From the release notes:

28 Oct, 2008: Ruby 1.9.1-preview1  
* Basically, the language features are frozen.
* But most of standard libraries need more changes for multilingualization.

The release notes also sets 25th December 2008 as the date for the release candidate, followed by the final 1.9.1 release on 25th January 2009.

InfoQ reported before about the changes in 1.9.1. One recent language change involves lambda. A patch by Eric Mahunin now allows the default values for arguments in lambdas. From the Changelog:

parse.y (f_block_optarg): allow default for block parameters as long as the value is primary. a patch from Eric Mahurin in [ruby-core:16880].

Another debated topic was the "stabby lambda", ie. the -> notation for lambdas, introduced in 1.9. While some were arguing for its removal, it remains in the language.

Dave Thomas (PragDave) mentions that the 3rd edition of the Pickaxe book (which covers 1.9.x) is done, and will be available around or after the final 1.9.1 release.

The Rubinius project has reached another milestone in it's development. Rubinius founder Evan Phoenix reports:

I’m super happy to announce that we’ve gotten the C++ branch stable enough that we’re making in the default branch. [..] Here is what was done:
* The old master branch was rename shotgun.
* The cpp branch was copy to the name master.
* The cpp branch was then deleted.

The C++ branch was started to rewrite the VM in C++. Previously, the "shotgun" VM was written in C. The new C++ VM is:

Better organized. We’ve learned a lot in the building of the last VM about how to structure things. For instance, using C++ lets us model Ruby classes as C++ classes, providing the VM with the same familiar structure and execution as their Ruby counterparts. [..] Better tested. The old VM, I’m ashamed to say, had no unit tests. From day one of the new VM, we’ve been writing unit and integration tests.

The Rubinius repository is available at GitHub.

No comments

Watch Thread Reply

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.