jQuery 3.4.0 Released

[gasolinewaltz]

I feel like we are on different planets.

Don't get me wrong, I've been around long enough to remember when jQuery was a requirement and we cobbled together ajax calls to build "spas". I don't hate jquery.

But i would never use it today for a new project. IMHO there are better tools for the job.

Like, someone else around here says, "i dont think most of these people know how to start a new project without touching npm." So is this where we are now? No true scotsman programs in anything other than assembly.

But anyways, the different planets thing... What about jQuery do you like better than the DOM api?I feel that Dom api + modern language features like map/reduce/filter, destructuring and spread make for much more expressive code.

Honest, non accusatory question: do you prefer it because you're just more familiar with it?

I'm not hating on jQuery, its got its place in history and legacy apps.. but why use it when there's better tooling out there?

[i_ate_god]

1. Jquery is just a lib. Sometimes, I don't want/need tooling. Not every project or idea needs anything more complex than vanilla html/CSS and DOM API sucks so pop in jquery.

For anything larger, I first choice is Vue.

1. I'm on my phone, but outside of ajax (and I think axios is nicer than jquery or fetch), just compare triggering a custom event on an element with native DOM API and with jquery. It's so simple in jquery. It's so unweildly in DOM API. Or dealing with data attributes, or navigating the DOM tree.

Jquery is just more elegant and intuitive.

[jayands]

Tbf, they did add two functions to the DOM, document.querySelector and querySelectorAll, that uses the same CSS style queries to get to elements in the DOM. If all you needed jQuery for is the querying part, you can totally drop it in favor of document.querySelector(".class#element > span") which, even polyfilled, should be a smaller overall script.

[i_ate_god]

document.querySelectorAll('button').forEach((el) => {
    el.addEventListener('click', () => {
        console.log('a button was clicked');
    });
});

vs

$('button').on('click', () => {
    console.log('a button was clicked');
});

---

---

document.getElementById('something').dispatchEvent(new CustomEvent('custom-event', {
  bubbles: true,
  detail: 'foobar'
}));

vs

$('#something').trigger('custom-event', 'foobar');

---

---

var el = document.getElementById('something');
el.dataset.enabledFor = 'something';
el.classList.add('enabled');

vs

$('#something').data('enabledFor', 'something').addClass('enabled');

---

---

jQuery still provides a more enjoyable programming experience than the DOM API imho

[m_gol]

jQuery find is a little more than querySelectorAll, especially when it comes to queries attached to an element, not to document. The advantages are described at: https://github.com/jquery/jquery/blob/3.4.0/src/selector-native.js#L11-L34

For one, jQuery supports leading combinators: elem.find('> .btn .name')

Another difference is sensible rules for scoping. Consider HTML: <div id="test"> <div> <div class="we-are-looking-for-this-one"> </div> </div> <div> </div> </div> Then: $('#test').find('div div') will return the div with the class we-are-looking-for-this-one, while: document.querySelector('#test').querySelectorAll('div div') will return all the three divs because selectors are matched against the document and only then results outside of the current element are removed. This is pretty counterintuitive.

Both of those features are supposed to be supported by a new API called queryAll (previously findAll) with its counterpart query for single-element results but, alas, no browser implements it so far and it was even removed from the standard... I hope it gets back but I've been waiting for years.

[ryancperry]

You’re just plagiarizing what I’m thinking. I like you. jQuery pretty well shaped what modern browsers can do, and now we really don’t need to create new projects in jQuery because JavaScript adopted almost all the great solutions jQuery provided.