Why we moved from NodeJS to Ruby on Rails

Re:Why we moved from NodeJS to Ruby on Rails by triathlete on Monday May 14, 2012 @02:32PM (#3972445)

I use node for everything now myself for a number of reasons. The "problem" with node is that its still very young. And its a different programming model then people are used to. So its similiar to the whole RDBMS/document store argument. You use what works for your applicaiton.

The thing that annoys me personally is that they make it seems like there something wrong with node. And there isnt at all.

[ Parent | on HN ]

Re:Why we moved from NodeJS to Ruby on Rails by andybak on Monday May 14, 2012 @02:34PM (#3972459)

Does it provide any of the functionality that you get with a Django/Rails style framework? Or is it at a lower level?

[ Parent | on HN ]

Re:Why we moved from NodeJS to Ruby on Rails by triathlete on Monday May 14, 2012 @02:44PM (#3972504)

Yes of course via express.js and railway and several other frameworks. Again node itself is just a set of libraries on top of of v8. So its not a proper comparison.

Personally i use express.js and roll my own framework essentially because i prefer to work that way.

[ Parent | on HN ]

Re:Why we moved from NodeJS to Ruby on Rails by andypants on Monday May 14, 2012 @07:30PM (#3973936)

There's are some web frameworks that are aspiring towards Django/Rails-style, but none that have a similar ecosystem of plugins and developers yet.

The most popular web framework, express.js, is a bit more lower level, and is similar to Werkzeug from Python or Sinatra from Ruby.

[ Parent | on HN ]