News for hackers. Stuff that matters.
Re:Is jQuery still relevant? (2014) by sAbakumoff on Wednesday January 25, 2017 @09:59PM (#13488353)
jQuery nowadays is much more than DOM manipulation lib. In the latest version it gives the promises that are compatible with Promises/A+ spec. It has the powerful ajax calls functions.
Re:Is jQuery still relevant? (2014) by oddstorms on Wednesday January 25, 2017 @10:52PM (#13488558)
They all moved on so they have no idea how good it is.
Re:Is jQuery still relevant? (2014) by sAbakumoff on Thursday January 26, 2017 @12:13AM (#13488941)
I mean instead of adding polyfills for "fetch" api and "es6 promises" that brings a gazillion dependencies with them, one can simply add jquery package that has ZERO runtime dependencies(https://github.com/jquery/jquery/blob/master/package.json) and have ajax calls, promises and much, much more out of the box. I love jQuery.
Re:Is jQuery still relevant? (2014) by untog on Thursday January 26, 2017 @01:02AM (#13489096)
Or you could add a fetch polyfill with zero dependencies:

https://github.com/github/fetch/blob/master/package.json

And a Promises library with zero dependencies:

https://github.com/stefanpenner/es6-promise/blob/master/pack...

This is not as difficult as you're making it out to be.

Re:Is jQuery still relevant? (2014) by sAbakumoff on Thursday January 26, 2017 @01:24AM (#13489169)
It's still 2 dependencies in your project versus 1 dependency.
Re:Is jQuery still relevant? (2014) by untog on Thursday January 26, 2017 @01:10PM (#13493693)
1 dependency that's 34.6KB minified. That's a lot more than the two separate dependencies, and besides, once you've gone to the trouble of adding a package.json to add one dependency, adding one more is a very small step.
Re:Is jQuery still relevant? (2014) by sAbakumoff on Thursday January 26, 2017 @09:57PM (#13497350)
where 34.6KB size came from? I don't get it