Migrating off jQuery? So was Sachin Neravath:

Most of the projects use only 15% to 20% or less than 30% of the jquery methods And in most of the cases, I didn’t want to support all the edge cases or legacy browsers. The hardest part was finding the jQuery methods in the existing project and writing the alternative vanilla js methods without making much changes in the codebase. So I wrote this library which automatically finds jquery methods in any particular JavaScript file and generates readable, chainable vanilla js alternatives. This can also be useful if you want to generate your own utility methods similar to jQuery.

We all love to hop on the latest JavaScript bandwagon - and there are some amazing things you can do with modern frameworks. Modern JavaScript and DOM APIs are much improved as well, with a movement to ditch jQuery in favor of vanilla javascript. But Martin Tournoij also has a pretty good case for why jQuery might still be pretty nice, starting with:

Pages like You might not need jQuery try to sell the idea that it’s easy to ditch jQuery, but the very first example is a good reason to use jQuery: one line of trivial jQuery code gets replaced with 10 lines of vanilla JS code!

It took years!

We’re finally finished removing jQuery from GitHub.com’s frontend. What did we replace it with? No framework whatsoever…

This is a long thread with some great conversations and questions.

What some people don’t not know is that you can incorporate Vue into your project the same way that you would incorporate jQuery, no build step necessary. You don’t have to rewrite the HTML in JavaScript, you don’t have to use webpack, and you don’t have to set up a giant system.

In this post Sarah Drasner covers common jQuery use cases and how to switch them over to Vue, and why you’d even want to.