agree plus add Rails is very well suited for the client side hotness with the asset pipeline in Rails 3.
However I just tossed Rails after many years for 2 primary reasons:
1) Anything that might take a sec or more has to be moved out of the request cycle and into a background process. That just gets annoying after a bit. Node.js can serve requests, grab data from to world's slowest API's, send emails, etc, all from a single process.
2) Although I think Ruby's strong point is readability and succinct LOC, it's hard to beat using the same language for everything and not context switching. Maybe my brain is broken, but I used to drive myself nuts writing client js and using Ruby's nil instead of null and Object.new instead of new Object.
For the project I'm working on now, I had to make my own asset pipeline. It uses less for css (and bootstrap), precompiles handlebar templates and concats all the js into a single file and uglifies it. Cost me 2-3 hours, about the same time it took me to learn Rails asset pipeline and was about 10x more fun.
Last point I'll add is when Rails was a baby it made fun of all the xml configs etc that other frameworks bogged developers down with. Now it's grown up a little, and although sprocket and yaml files aren't xml, the concept is the same. If you've been around Rails for awhile and dive through the code of project like Spree, you just scratch your head and little simple things like node appear shimmering sexy!
> For the project I'm working on now, I had to make my own
> asset pipeline. It uses less for css (and bootstrap),
> precompiles handlebar templates and concats all the js
> into a single file and uglifies it. Cost me 2-3 hours,
> about the same time it took me to learn Rails asset
> pipeline and was about 10x more fun.
However I just tossed Rails after many years for 2 primary reasons:
1) Anything that might take a sec or more has to be moved out of the request cycle and into a background process. That just gets annoying after a bit. Node.js can serve requests, grab data from to world's slowest API's, send emails, etc, all from a single process.
2) Although I think Ruby's strong point is readability and succinct LOC, it's hard to beat using the same language for everything and not context switching. Maybe my brain is broken, but I used to drive myself nuts writing client js and using Ruby's nil instead of null and Object.new instead of new Object.
For the project I'm working on now, I had to make my own asset pipeline. It uses less for css (and bootstrap), precompiles handlebar templates and concats all the js into a single file and uglifies it. Cost me 2-3 hours, about the same time it took me to learn Rails asset pipeline and was about 10x more fun.
Last point I'll add is when Rails was a baby it made fun of all the xml configs etc that other frameworks bogged developers down with. Now it's grown up a little, and although sprocket and yaml files aren't xml, the concept is the same. If you've been around Rails for awhile and dive through the code of project like Spree, you just scratch your head and little simple things like node appear shimmering sexy!