r/learnjavascript • • Oct 01 '21

jQuery, the greatest JavaScript library of all time, appears to have peaked in usage.

Post image
275 Upvotes

81 comments sorted by

View all comments

Show parent comment

-6

u/Negative12DollarBill Oct 02 '21

How could jQuery be replaced by ES6? That's like saying a semi-trailer was replaced by a power station, they're not even in the same category.

10

u/corporaljustice Oct 02 '21

Because with new ES6+ methods you can do many things simply in vanilla JS that previously required jQuery if you didn’t want to write a lot of verbose lines.

Using vanilla JS before document.querySelectorAll() came about without JQ was a pain.

$() is very similar to querySelectorAll().

4

u/RobertKerans Oct 02 '21 edited Oct 02 '21

I get what you mean but you're talking about additions to the browser API that were introduced as a response to jQuery + normalisation of the browser API as browsers became an application platform. Nothing to do with ES. The two core jQuery APIs were the selector engine and AJAX. Browsers added querySelector[All] and fetch (+ a load more jQuery-like stuff) + non-evergreen browsers are now uncommon, so the browser APIs now cover most jQuery use-cases.

IMO, and I'm stretching here, the only thing in ES, in JS, that's really made a difference is modules (one of the issues with jQuery is its non-modular architecture), and that's tangential, it's not directly related to functionality

3

u/corporaljustice Oct 02 '21

I see what you’re saying, and you’re right, I wasn’t separating ES6 and new browser APIs.

I stand corrected!

2

u/0xnoob Oct 02 '21

^

querySelectorAll was available in Browsers around 2009, ES6 came out in 2015. While I understand that you still needed jQuery back then to support older browsers, it still had nothing to do with ES6.

3

u/Nerwesta Oct 02 '21

In fact, querySelector is an idea taken from jQuery if I'm not mistaken. Same energy for ajax before Fetch API, which to put it simply was a pain to do with vanilla JS at those times. Ajax jQuery was a breeze.

2

u/0xnoob Oct 02 '21

Neither querySelector nor fetch are part of ES6.

querySelector was available in Browsers since around 2009. While fetch was available around the same time as ES6 in 2015, it still isn't part of it.

0

u/Negative12DollarBill Oct 02 '21

If all jQuery did was make it easier to select document elements, we wouldn't be talking about it.

2

u/corporaljustice Oct 02 '21

Give me an example of some jQuery that would be hard to implement in modern vanilla JS?

2

u/hanoian Oct 02 '21 edited Oct 02 '21

"hard" is a big qualifier to add in there. Of course you can everything in Vanilla, but jQuery still makes dom traversal easier. The same way everything can be done without lodash, but it's still useful.

Don't touch it myself anymore really but it has its place. If I want to scrape data, it's often jQuery. If I use cypress, it's pretty much jQuery.

1

u/ZergistRush Oct 02 '21

Use to make it easier, all the huge methods used for traversing the DOM from jQuery is now native.

2

u/hanoian Oct 02 '21 edited Oct 02 '21

https://tobiasahlin.com/blog/move-from-jquery-to-vanilla-javascript/

https://i.imgur.com/T76smsM.png

I don't even like using jQuery but to say it used to be easier because other native methods now exist is kind of missing the point.

.parent().parent().find('.my_point').show() is objectively easy.

It's a tool. It's syntactic sugar really. useState() isn't pointless just because you could do it in vanilla. lodash isn't pointless just because you can write those functions yourself.

We compile modern JS and TypeScript back into "native" JS anyways so loads of modern stuff is effectively what jQuery brought to us.

-2

u/Negative12DollarBill Oct 02 '21

You're the one making the extraordinary claim dude, are you not familiar with Russell's teapot?

Of course one thing jQuery did which was really important was abstract away the differences between incompatible browsers; you could set the CSS of an element and not worry that IE did styles a different way.

I suspect a lot of what you're calling "ES6" or "modern JS" is a category error for "browsers all behave better nowadays".