The history and legacy of jQuery
There&#x27;s another reason to use jQuery not included in the article, albeit one which has lost a bit of relevance in the last few days:<p>jQuery plugins&#x2F;extensions&#x2F;libraries&#x2F;whatever.<p>An awful lot of libraries for things like carousels and masonry type grid systems and other such things are built with jQuery as a dependency, so anyone wanting to use them (especially to avoid rolling out their own version) is stuck relying on it.<p>Fortunately, a lot of these things have either moved to working as standalone vanilla JS type deals, or to NPM modules instead.<p>Unfortunately, the latter is argubaly causing the same dependency hell issue, since many devs will now basically throw in a full JavaScript framework and a bunch of task builders and managers like webpack just to be able to include said modules more easily and save on development time&#x2F;costs.