Isn't it frustrating when 2 equally "tempting" web technologies compete for your preference, if you're a developer, and for your resources if you represent a company? Take these 2 highly popular technologies which have divided the web community into 2 groups: each one of them comes with its own heavy load of advantages, balanced by their sets of drawbacks, too! In conclusion: in the Node.js vs Ruby on Rails debate there's no such thing as “THE technology that fits all use cases and scenarios”. There's only “THE one that makes the best fit for... you”: for...