> the current JavaScript landscape seems to have a fairly low index; there are a huge number of tools with very few clear winners at this point in time This is

> the current JavaScript landscape seems to have a fairly low index; there are a huge number of tools with very few clear winners at this point in time This isn't a problem by itself, the problem is the ever-changing "clear winners" and hordes of people using them with no understanding of their trade-offs. I hear complaints like this a lot: "It was so easy to-do this with jQuery, why is this JS-framework-de-jour so complicated?" - well, why didn't you start with what-you-know and explore their limits litte bit, so you would know what you really needed? With Ruby and Rails, you have a single answer to many use-cases, with JS and the npm, you have many answers to each use-case imaginable and choosing by popularity is very damaging.