IDGNS: So removing elements is to keep Rails simple and lightweight?

DHH: Yes. We don't believe that just because at one point back in the day we included an experiment, or chose to do an API, that it's going to stay for ever. We don't want to turn into Java, this pack rat that just keeps hold of any possession. We're not afraid to take out stuff that's not relevant or we plain don't like. That's important to keeping it a light and friendly framework.

IDGNS: Do you have an updated release date for 2.0?

DHH: I might be giving one, it depends how things shape out. We've maintained that we hope to complete it this year. This is an open-source project founded on desires to get things done, things wax and wane, so we don't have a traditional road map, and we definitely don't try to pin down shipping dates.

IDGNS: Some people have said we should have a standard implementation of Ruby to prevent splintering. What do you think?

DHH: There's definitely talk about making Ruby a specification that can be implemented in JRuby or IronRuby (a version of JRuby for Microsoft .Net), I know there are some people who are moving along in that aspect, and that would be nice. None of them impact me on a day-to-day basis. I'm happy with the implementation of Ruby done by Matz [Ruby creator Yukihiro "Matz" Matsumoto]. The JRubys and IronPythons are niches; that's not what's being used by the majority of Rails users.

IDGNS: But enterprises are interested in JRuby because they can use Rails on their existing Java servers....

DHH: JRuby is a great way to open the conversation with enterprises by saying, You don't have to throw out all this "junk" you've accumulated over the years, Ruby is just an incremental piece you can put in. But in some ways, it's sugar coating to get people to really come on board. It's a bridge for getting from one place to another.

The majority of Ruby on Rails users out there are people who go straight to Ruby on Rails, they don't have junk in the trunk. And they are still by far the highest number of users. The enterprise is a fairly newcomer.

IDGNS: So what's Rails being used for mostly today?

DHH: The vast majority is Web applications, that spans public Web sites, some for Web 2.0-ish applications, some e-commerce solutions, we're building collaboration tools. Any application that's a good fit for delivering through a browser is a good fit for Ruby on Rails, from the shaded gradients of Web 2.0 to mortgage processing applications for detecting credit ratings.

IDGNS: Where would you like to see it really succeed? What's your dream for Ruby on Rails?

DHH: My dream is that people adopt it on its own merits. We're not trying to bend Ruby on Rails to fit the enterprise, we're encouraging enterprises to bend to Ruby on Rails. Come if you like it, stay away if you don't. We're not going head over heels to accommodate the enterprise or to lure them away from Java. That's how you end up with Java, if you start bending to special interest groups.

We'll continue to add techniques and technologies that work for us, and it's great if it works for other people too, but Rails is very much an egotistical brainwork for me. I care about designing for me and producing a framework that works great for me, and that's the only constituent I have in mind when I develop it.