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.

Getting started with Rubinius development

Posted by Werner Schuster on Sep 28, 2007

Sections
Development,
Architecture & Design
Topics
Programming ,
Ruby ,
Technology ,
Dynamic Languages
Tags
Trends ,
Rubinius
Rubinius has been getting a lot of support recently, and some in the group of Ruby VM implementers believe it to have a grand future

One of the reasons is the modular design and how Rubinius exposes its internals. Rubinius is well suited for new developers trying to help out, as it takes introspection all the way. Ruby already makes it trivial to inspect a Ruby class with methods such as obj.methods(shows the methods of obj). Rubinius goes one step further by giving access to the Abstract Syntax Tree (AST) of the Ruby code, a data structure representing the code. Rubinius uses ParseTree, a representation using symbols and nested lists. For example, this code:
puts "Hello, Rubinius. You rock my world!"  
is represented like this:
 [:fcall, :puts, [:array, [:str, "Hello, Rubinius. You rock my world!", 0]]] 
If this looks familiar to LISP or Scheme code, that's no accident. The representation is called s-expressions (symbolic expressions), which is also how these languages represent their code.

The benefit of representing an AST this way is that it's easier to read than a data structure made up of linked objects in memory. This becomes even more evident for creating ASTs, for instance for test cases using ASTs.

Reading up on ParseTree can be helpful for working on Rubinius. A couple of tools are already based on ParseTree. Ruby2Ruby takes an ParseTree AST and turns it into Ruby source code - useful for looking at runtime generated Ruby code. Flog is a new tool that analyzes code an generate a quality rating of it. Other tools based on ParseTree, such as Ruby2C or Heckle can provide some insights as well. Another use of ParseTree can be seen in the Ambition, a way of using ParseTree representation of Ruby code to create database and other queries.

Brian Ford discusses Rubinius internals, like getting ParseTree output. Among the topics are tools for looking at ParseTree ASTs for Rubinius code and the underlying bytecode for the code. This allows new Rubinius developers to quickly figure out is going on under the covers or what Ruby source is turned into for execution. More and updated details and command line options can be found in the Rubinius Wiki on Command line options.

For everyone now interested in looking at Rubinius code, Sam Aaron put together a list of links and instructions to get started on Mac OS X. One aspect, that might be problematic for new developers, is the source code management (SCM) system Rubinius uses. After using Subversion for some time, the team recently switched to Git. Git is a Distributed SCM, originally written by Linus Torvalds for Linux Kernel development, but an increasing number of projects are using it too. Distributed SCMs are increasingly popular, as they faciliate branching which allows for easy experimentation

To get started, see Using Git page at the Rubinius website. Once Rubinius is checked out, it's easy to keep up with the development using Git, as Sam Aaron points out:
Head to your Rubinius directory and utter forth the following:
git pull ; rake build
Git by Guy Coleman Posted
Re: Git by Werner Schuster Posted
Re: Git by Guy Coleman Posted
an or and by Su Yu Posted
  1. Back to top

    Git

    by Guy Coleman

    Unfortunately using Git means it's much harder to develop on Windows.

    The Linux kernel developers may all be using a certain free UNIX clone, but I bet there are one or two Ruby developers on Windows..

  2. Back to top

    Re: Git

    by Werner Schuster

    Git seems to work on Windows:
    git.or.cz/gitwiki/WindowsInstall
    No idea how well it works though.

    There seems to be a Java Git client and an Eclipse plugin
    git.or.cz/gitwiki/EclipsePlugin

    It's somewhat surprising (to me at least) that many projects now seem to choose Git, especially since it was designed for Linux Kernel work on Linux. I'd have thought that Mercurial www.selenic.com/mercurial/wiki/
    would be the choice for non-Linux Kernel projects. It's used by many projects
    www.selenic.com/mercurial/wiki/index.cgi/Projec...
    and (from what I know) was one of the two final candidates as DSCM for Rubinius.

  3. Back to top

    Re: Git

    by Guy Coleman

    It works, for some value of "works" :-)

  4. Back to top

    an or and

    by Su Yu

    Flog is a new tool that analyzes code an generate a quality rating of it OR
    Flog is a new tool that analyzes code and generate a quality rating of it

Educational Content

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.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.