Let’s also not forget “half of what we’re using frameworks for has been directly supported by every browser since 2011 but we still have a dependency on a framework that extends another framework that hard-requires jQuery as a selector engine so we’re not going to remove any of them”.
It’s kind of depressing to ship two megabytes of dependencies for something a hundred lines of vanilla JS would do just fine these days. But of course it’s far easier to maintain external code than int– oh wait, one of our dependencies switched a dependency and now security needs to re-evaluate the stack before we can install the latest security-relevant update.
Let’s also not forget “half of what we’re using frameworks for has been directly supported by every browser since 2011 but we still have a dependency on a framework that extends another framework that hard-requires jQuery as a selector engine so we’re not going to remove any of them”.
It’s kind of depressing to ship two megabytes of dependencies for something a hundred lines of vanilla JS would do just fine these days. But of course it’s far easier to maintain external code than int– oh wait, one of our dependencies switched a dependency and now security needs to re-evaluate the stack before we can install the latest security-relevant update.