JavaScript was originally a way to create interactive webpages, but because it broke or replicated MVC, became the backend too. The variety of backend requirem

JavaScript was originally a way to create interactive webpages, but because it broke or replicated MVC, became the backend too. The variety of backend requirements, and the flexibility of UX, led people to solve many individual workflow bottlenecks or generalize to any/many. Then so, like the English language, exploded to the simple-->jargon range of overloaded usage and niche comprehension, very quickly fragmenting, but universally powerful. Developing a framework as a startup for a particular use case may take more time than prototyping on an existing framework--this is why the prototype should be discarded, and a critique of how open source/reusable code has always been a source of technical debt apart from the rare, shining outliers.