Further Insights into Rhino on Rails

| by Nick Laiacona Follow 0 Followers on Feb 10, 2008. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Dion Almaer has published a podcast of his interview with Steve Yegge, the creator of Rhino on Rails. An earlier blog post by Steve generated a significant amount of interested by the developer community.  Rhino on Rails is a Javascript port of the popular Ruby on Rails framework. It is currently under active development for internal use at Google. Steve Yegge and his team hope to make Rhino on Rails open source this summer. Yegge first announced last summer at Foo Camp and in his blog. Questions Almaer asked:

  • What does it mean to port Rails to JavaScript?
  • What can't you do since JavaScript doesn't have the same meta programming facilities?
  • Rails = a group of Active*, so did you re-implement everything?
  • What do you gain out of having JavaScript all the way down?
  • Does it actually make sense to have jjs? Server side JavaScript generating client side JavaScript? Argh!
  • What is the state of Rhino?
  • Will Rhino support JavaScript 2?
  • How does the JVM help you out?
  • What are the ramifications of implementing ActiveRecord with Hibernate
  • Fun other languages to play with

Yegge revealed some interesting details of the project during the interview. The principal reason he choose to port Rails to Javascript on the JVM is the support Javascript enjoys within the Google corporate environment. Rhino on Rails is a true port of Ruby on Rails, starting from version 1.2. Users of Ruby on Rails should find Rhino on Rails's API familiar. It does not currently include Active Record, the powerful domain model library on which Rails database model objects are built. However, Yegge is aiming to add this functionality. When released, Rhino on Rails will probably operate within a Jetty container. It may also contain support for GWT. Yegge points to concurrency support in Rhino on the JVM and his implementation of Rails as scalability advantages over Ruby on Rails.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you