4 ms·

Thank you. As a Ruby on Rails programmer I couldn't agree more. Rails 3.0 will bring some maturity... programming to interfaces and APIs rather than implementat

Thank you. As a Ruby on Rails programmer I couldn't agree more. Rails 3.0 will bring some maturity... programming to interfaces and APIs rather than implementations. I believe Javaland "got that" a long time ago.

gfodor 16y ago
Agreed. Rails 3 seems to be shaping up to be the "revenge of the grown-ups". I see it as potentially being as paradigm shifting as the initial release of Rails, but not as in-your-face. When Rails came out, it reminded us that programming can be fun. Rails 3 will shows us that not only can it be fun, but it doesn't have to come at the cost of stable interfaces, reusable code, and the ability to not have to go back and refactor your entire project every 6 months.
- shimonamit 16y ago
  Thank you Merb people.
- dhh 16y ago
  I think it's awesome that you're excited for Rails 3. I'm incredibly excited for it. Lots of great stuff happening. But. (And that's a big but). I think you might overestimate the philosophical changes that are going on here. Seeing pipe dreams and unicorns where there are simply just incrementally improved ideas and work horses. The rate of improvement in the Rails camp is not going to change because of anything fundamental to Rails 3. It might change because we're running out of big problems to deal with, but I also somewhat doubt that. So that means that yes, you will have to change your application every 6 months, if you want to keep up with the latest and greatest. But you don't have to. You never had to. A Rails 2.3 application, for example, could have been chugging along just fine for the last 12 months (2.3.0 released March '09).
hopeless 16y ago
If only the language itself was on the same solid footing! I love Ruby on Rails but I see most of the uncertainty coming from broken Ruby 1.8.7 and 1.9 builds -- Rails changes just add to the mess.
- grk 16y ago
  Rails 3 + Ruby 1.9.2 should be fine.

gfodor 16y ago

Agreed. Rails 3 seems to be shaping up to be the "revenge of the grown-ups". I see it as potentially being as paradigm shifting as the initial release of Rails, but not as in-your-face. When Rails came out, it reminded us that programming can be fun. Rails 3 will shows us that not only can it be fun, but it doesn't have to come at the cost of stable interfaces, reusable code, and the ability to not have to go back and refactor your entire project every 6 months.

shimonamit 16y ago
Thank you Merb people.
dhh 16y ago
I think it's awesome that you're excited for Rails 3. I'm incredibly excited for it. Lots of great stuff happening. But. (And that's a big but). I think you might overestimate the philosophical changes that are going on here. Seeing pipe dreams and unicorns where there are simply just incrementally improved ideas and work horses. The rate of improvement in the Rails camp is not going to change because of anything fundamental to Rails 3. It might change because we're running out of big problems to deal with, but I also somewhat doubt that. So that means that yes, you will have to change your application every 6 months, if you want to keep up with the latest and greatest. But you don't have to. You never had to. A Rails 2.3 application, for example, could have been chugging along just fine for the last 12 months (2.3.0 released March '09).

hopeless 16y ago

If only the language itself was on the same solid footing! I love Ruby on Rails but I see most of the uncertainty coming from broken Ruby 1.8.7 and 1.9 builds -- Rails changes just add to the mess.

grk 16y ago
Rails 3 + Ruby 1.9.2 should be fine.