4 ms·

I ditched rails long ago because it's simplicity was an absolute nightmare when you actually wanted to build something that wasn't a clone of basecamp. From my

by jpcx01 17y ago

I ditched rails long ago because it's simplicity was an absolute nightmare when you actually wanted to build something that wasn't a clone of basecamp. From my experience so far, Rails3 is a breath of fresh air. Easy to get up and running, and also easy to extend and replace the pieces you dont want. My current Rails3 app doesnt use any ActionView at all (used my own view system) and its working great so far. This wouldn't have been even remotely possible in Rails 2.3.

jamesbritt 17y ago
"From my experience so far, Rails3 is a breath of fresh air." I'm curious to know if you've tried any of the dozen or so other Ruby Web frameworks, such as Ramaze, Camping, Sinatra, IOWA, Waves, etc.? It seems that the things people seem so excited about in Rails 3 have been available since, say, Nitro, four or five years ago.
- jpcx01 17y ago
  Yup, tried them all (merb was the one i landed on for core dev work). So far Rails3 seems much better than all of them. Community, documentation matter. Also having an active core team. Rails 3 seems like the best of breed web framework for now.
teilo 17y ago
Not having even played with Rails since the 1.x days, I find this all very interesting. I have been using Django for a while now, and what you describe here is exactly what impressed me about Django. If I didn't like something in the core, it was trivial to switch it out. I tried 4 different templating engines within a two week period, and that was when I was a Django newbie. I think the author of this article needs to get out a bit and look around at the rest of the web framework world. Rails building on existing components is Not A Bad Thing, because it means that Rails has taken a decided turn away from being a monolithic framework toward being a set of well-formed but loosely coupled components. Light as a feather, stings like a bee, baby. Looks like I'll be playing with Rails 3 in the near future.

by jpcx01 17y ago

jamesbritt 17y ago

"From my experience so far, Rails3 is a breath of fresh air." I'm curious to know if you've tried any of the dozen or so other Ruby Web frameworks, such as Ramaze, Camping, Sinatra, IOWA, Waves, etc.? It seems that the things people seem so excited about in Rails 3 have been available since, say, Nitro, four or five years ago.

jpcx01 17y ago
Yup, tried them all (merb was the one i landed on for core dev work). So far Rails3 seems much better than all of them. Community, documentation matter. Also having an active core team. Rails 3 seems like the best of breed web framework for now.

teilo 17y ago

Not having even played with Rails since the 1.x days, I find this all very interesting. I have been using Django for a while now, and what you describe here is exactly what impressed me about Django. If I didn't like something in the core, it was trivial to switch it out. I tried 4 different templating engines within a two week period, and that was when I was a Django newbie. I think the author of this article needs to get out a bit and look around at the rest of the web framework world. Rails building on existing components is Not A Bad Thing, because it means that Rails has taken a decided turn away from being a monolithic framework toward being a set of well-formed but loosely coupled components. Light as a feather, stings like a bee, baby. Looks like I'll be playing with Rails 3 in the near future.