The nature of the javascript type system means that large software systems written in it are built on very shaky foundations. This means that it's very easy to

The nature of the javascript type system means that large software systems written in it are built on very shaky foundations. This means that it's very easy to build a framework but also that it's very likely for a framework to break and under sustained, real life use cases. This led to a cycle whereby javascript developers would get excited at the potential of a new framework, use it IRL and then get disillusioned before getting excited about another new framework. I think this also drove the average age of javascript developers down (older developers were less patient with this pace of change) and this cycle sort of fed on itself too, as younger developers are more likely to jump on something new. And, a large part of it is simply that javascript is an incredibly popular (possibly the most popular) language. From what I understand this cycle has kind of come to a halt now and most people seem to default to react and the type system is getting a little less train-wreck-y with stuff like typescript.