| ... you can just architecture it to be SOA or with tons of microservices. I think Node.js is hype right now and you'll be betting on a technology that may or may not have a good market share. RoR is better and have tons of documentations and blogs. Node.js right now just got forked. Javascript isn't a particular pretty language compare to Python or Ruby. Loosely type and dynamic makes it kinda bad. I have yet to see any body mastered Javascript as a language and Javascript 6 or ECMA or whatever is coming out. So there is even more stuff to learn. The dev pools for javascript for backend is sparse and their language mastery, from my experiences, for javascript is very low. With that in mind hey you didn't learn prototype OOP yet but guess what we're going to add more to the language and hope that those dev catch up to all of the changes? yeah... That's a con to be at least. And also Ruby while they're changing with every version it's small iteration, most of the stuff is mostly in place. Javascript is missing a few construct to build large code base, namely module which they will have a standard soon, and going to add promise construct cause node.js callback hell is bleh. So the language wasn't multi purpose in mind so it's playing catchup. You can argue that you can do anything with a turing complete language. Sure you can, but how easy it is should be a factor. Erlang got primitives for spawning process and such. It makes it damn easy. Javascript got little construct for building large code base. THere are tons of libraries to fix this but still. I think Node.js ss better as a middleware technology and even then Go would be a better choice with better toolings. |