InfoQ

News

Getting started with Rubinius development

Posted by Werner Schuster on Sep 28, 2007 12:01 AM

Community
Ruby
Topics
Technology,
Dynamic Languages,
Programming
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

5 comments

Reply

Git by Guy Coleman Posted Sep 28, 2007 3:25 AM
Re: Git by Werner Schuster Posted Sep 28, 2007 5:38 AM
Re: Git by Guy Coleman Posted Sep 28, 2007 9:40 AM
an or and by Yu Su Posted Sep 28, 2007 10:09 PM
Re: an or and by berkay NiQuiL Posted Jun 30, 2008 3:05 PM
  1. Back to top

    Git

    Sep 28, 2007 3:25 AM 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

    Sep 28, 2007 5:38 AM by Werner Schuster

    Git seems to work on Windows: http://git.or.cz/gitwiki/WindowsInstall No idea how well it works though. There seems to be a Java Git client and an Eclipse plugin http://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 http://www.selenic.com/mercurial/wiki/ would be the choice for non-Linux Kernel projects. It's used by many projects http://www.selenic.com/mercurial/wiki/index.cgi/ProjectsUsingMercurial and (from what I know) was one of the two final candidates as DSCM for Rubinius.

  3. Back to top

    Re: Git

    Sep 28, 2007 9:40 AM by Guy Coleman

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

  4. Back to top

    an or and

    Sep 28, 2007 10:09 PM by Yu Su

    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

  5. Back to top

    Re: an or and

    Jun 30, 2008 3:05 PM by berkay NiQuiL

Exclusive Content

Rationalizing the Presentation Tier

Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.

Agile Project Management: Lessons Learned at Google

In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.

AtomServer – The Power of Publishing for Data Distribution

In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.

An Introduction to Virtualization

It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.

REST Anti-Patterns

In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.

Choosing between Routing and Orchestration in an ESB

In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.

Enterprise Batch Processing with Spring

Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.

User Story Estimation Techniques

Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.