I recently read Arun’s blog entry on getting the Mephisto blog engine running inside Glassfish. It has gotten easier since about a month ago, when it was necessary to use GoldSpike to package the Rails app into a .war file before deploying it to Glassfish. The reason I bring this up is that during the question and answer portion of the Ruby on Rails: To Scale or Not To Scale talk, Glassfish came up. Jason Hoffman, CTO of Joyment, said that running a (test?) Rails app in Glassfish showed that it could handle five times the number of requests per second as Mongrel. One of the thought provoking comments that Jason made was, what if Glassfish became the defacto standard for running Rails apps, and subsequently JRuby became the preferred Ruby implementation? Continuing that thought, he asked, who then drives the definition of the language? Likewise, many newcomers to Ruby are learning it because of Rails. What if Rails drives the direction of Ruby, as well.
Admittedly, I had not considered such questions. I’ve been too excited about learning Ruby and Rails to stop and think about its future. It looks to me like it’s in good hands, so I’m not the least bit worried. I’ll just focus on writing apps, until the next language and framework come along.