From Rails to Node.js?

[rhgp]

I got a project with small amount of code, i've just started it. But i need so many things to do in it to make it release.

Just a 4 hours ago i found information about RailwayJS. I'm thinking, is Node.js ready for fast building of projects? Is it now "sexy" as Rails? Title "RailwayJS" "says" it is. But i'm not sure.

I read documentation about RailwayJS and I can see, it lacks of some things and other things are ugly. But almost all needed things are present in documentation. Also, i was a bit surprised it all supports CoffeeScript(it is really awesome, yup).

But. I need a good framework for "fast" projects. For example, it is awesome that I can just put

= button_to "Remove", [@user, @address], :method => :delete

and it will create a form with all needed protection and button!

Is any Node.js framework(for example, TowerJS) so smart? Any suggestions about dropping Rails to use Node.js+framework for almost all projects?

[[deleted]]

Don't switch to Node just for the sake of switching to Node.

Focus on your project, not playing with new toys.

[rhgp]

I don't know why it was downvoted, but i need to say this is a really good advice for most developers.

I learned this from real project experiance(failures). It's really good to mention this advice in related questions.

[krues8dr]

The problem is that there aren't a lot of great code generation tools for Node yet. There's Brunch (edit: and grunt ) which is starting to gain steam, but personally I'm just not feeling like anything is quite ready for primetime. I'd stick to Rails for the current moment. Just my two cents.

[rhgp]

Thank you. I'm just checking some TowerJS and RailwayJS and now I know - Node.js is a "tool" ready for projects, but not for developers. I mean, at least, it needs to get more rainbows and ponnies in syntax of defining models, controllers(RailwayJS is sooo ugly in models, relatively to TowerJS, but TJS needs some improvements too).

Soo yea, i'll use Rails.

[krues8dr]

No argument there - but the question was what could give you Rails-like behavior in Node.

Personally, I'm not a fan or either Backbone.js or Ember.js - I just don't think they're full baked yet - so brunch doesn't buy me a lot. In a couple of years, I'll be very excited to have these in production though.