there's a couple of things at play * JS's history is all about "quick and dirty". jQuery in older times was meant to paper over the quick and dirty and give de

there's a couple of things at play * JS's history is all about "quick and dirty". jQuery in older times was meant to paper over the quick and dirty and give developers more convenience, and old JS without JQuery was pretty awful * we are asking JS to do things it was never meant to do; in particular, the desire for "app-like" experiences and SPAs. * JS is very backward compatible, which means old webpages can be archived, but also means that all the warts are still around. * JS interpretation depends on browsers, which means if you want to use some modern features you will have to use some kind of transpiling, polyfill, and or framework to get some consistent behavior on all of them (jQuery in older times, babel today), and the differences in browsers means that these adapters have to be mind-bogglingly complex a lot of times