I see two questions 1) Is OOP bad 2) Should Composition be favored over Inheritance (this question assumes that oop is not bad, because both inheritance and composition comes within the context of OOP) Answer to 1- I hear a lot of kids say that, but i dont see them explaining any thing convincingly. OOP was an improvement over procedural thinking. The real fact is oop is pretty hard to comprehend and oops generally is implemented the way, the dominant developer sees the domain. It takes some effort to understand and learn oops and apply them practically. OOPs is meant for re usability, maintainability ,extensibility at the very least. There is another programming style called functional programming style. Javascript is one where functions are passed around. I think by the time the client side JS frameworks like angular started to prosper, OOPs had become defacto industry standard and ppl attempted to write oops style in JS which is where the problems started evolving 2) On this question. yes composition should be favoured over inheritence. I prefer inheritence for data (property) reuse and composition for behavior encapsulation

Node JS rocks when it comes to io. Club it with Nginx and you get scalable systems. IMHO NodeJS/Nginx lets you get most out of your hardware. My experience is limited to using it for io based operations and dude it rocks. The only glitch i see is that it is hard to write object oriented equivalent code. Just create an eco system of small serverices that is built on NodeJS I have not used node JS for projects having high computing requirements (read processing requirements). There are now a lot of libraries and different ways of dealing with such things in Node, but i have not tried it myself. It would be interesting to see if any one used Node for projects having high computational requirements in production and how it scaled and what challenges they faced. In this world, alas there is no single tool for all different problems and we need to acknowledge it