Should I stop using jQuery after ES6 release?

Looks like most of the things that you do using jQuery can be easily achieved via ES6 implementation.

Example 1

jQuery
$(el).children();

ES6
el.children

Example 2

jQuery
var $items = $container.children('.item');

$items.hide();

Vanilla JavaScript

let items   = h.children(container, '.item'),
    item    = null,
    i       = -1;

for (i = 0; item = items[i]; i++) {
    item.style.display = 'none';
}

ES6 already released. It is a current standard for almost a year and ES7 is coming. Probably you are confusing ECMAScript2015 (ES6) and ECMAScript 2016 (ES7).
Actually you should dropped jQuery since ES5 which added querySelectors, classLists, forEach and many other stuff. All your examples, are just old vanilla JS, even older then ES5. Still, of course, ES6, has new features also.
Yes, you should drop jQuery since it was invented 10 years ago in a time when we had problems with JS standard and it implementation. Every browser had own API and many DOM APIs were missed these times. jQuery use case was a simple cross-browser scripting and nothing changed. Now you don't have that problem. The jQuery problem is, you need to include at least jQuery core which is huge and vanilla JS, of course, is the fastest approach for browser scripting. Let be honest, we never needed jQuery in our apps, we needed widgets like autocompletes, select2, form validation and everything else. We imported jQuery only because those libraries asked for so. Problem here is that still today we have too less good Vanilla JS libraries but we have over 9000 same plugins for React/Angular and everything else. That's why I created https://bunnyjs.com - set of Vanilla JS librares, helpers and widgets. If you just want to display data from the server via ajax, you only need to import one small file and you are ready to go.

This is one of those questions that depends pretty heavily on the browsers you need to support. If you only need to support the evergreens, you probably don't need jquery (or as the site says, YMNNJ http://youmightnotneedjquery.com).

Also if you work on an established product that can't work without jQuery, you might find it's not worth the overhead. More so if you work with other people who haven't learned ES6 yet.

ES6, or ES 2015, doesn't solve anything about jQuery. The first is sugar versus ES5 and the second was a great utility last ten years, or seven in my case, but now we've need to think different (...sorry) with functional paradigm, components, shadow or virtual dom, immutables data, etc.

Problem with ES6 is yet the proper browser support though.. Not everybody should have a fully loaded stack configuration just to use some ES6 Features .. I think it depends on the project target to use jQuery or not..

Thread

Should I stop using jQuery after ES6 release?

Example 1

Example 2

Responses(4)

Recent threads

Search Hashnode

Should I stop using jQuery after ES6 release?

Example 1

Example 2

Responses(4)

Recent threads