Skip to content

Comment on Why Everyone Is Talking About Node

Comments

It's more like "Everyone is talking less about Rails" - the only new kid in Rails block is Haml/Sass and Rails is obviously stagnating compared to the hype it had couple or more years ago. Ruby/RoR is more about evolution now: Rubinius, JRuby going for stability, SalesForce adopts Heroku as one of it's development platforms - look, even one of Big 4(DTT) hires RoR-consultants now.

JavaScript on the other hand is booming both on client (SproutCore, Backbone, Cappuccino, CoffeeScript, GWT) and on server (Node). JS is just more "hackish" today - browsers are evolving day-by-day, taking more and more functionality from server - RoR isn't key to success anymore, it has become just another alternative for your REST backend.

Not sure it's fair to say Rails is stagnating. Rails 3 (particularly with the improvements in ActiveRecord) is significantly leaner and nicer to use than Rails 2.

"stagnating __compared to the hype it had couple or more years ago__"

New API for ActiveRecord, modularity, merging with Merb are very important, but it's not a game-changer. Rubinius and RubyMine on the other side are game-changers.

I welcome the stagnation! We started development with Rails when it was at 0.7, and the pain of keeping up with a rapidly developing framework was something I felt some level of resentment for.

I wouldn't say Rails is stagnating, I'd say it is maturing.

For me it's about simplicity. RoR has become a beast almost of asp.net/IIS proportions. I'd rather not deal with the hassle of getting everything set up. That's why I'm in love with Sinatra, Node, and golang.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.