Live data from Hacker News

jQuery 3.6.0

blog.jquery.com

1–10 of 292 posts

Re: jQuery 3.6.0

#4

> We still have our eyes on a jQuery 4.0 release, but until then we will continue to support the 3.x branch and address important issues.

This caught my eye too. What could they be cooking?

Re: jQuery 3.6.0

#6
Do people still use jQuery?

I thought the biggest advantage of this library back in the day was css selector access of DOM nodes (back when we only had getElementById, getElementsByClassName, and getElementsByTagName). This has been rolled into the Javascript document api via document.querySelector, and document.querySelectorAll.

Also there are browser compatibility issues that jQuery solved but a lot of these are solved with smaller footprint libraries like lodash.

Also for me, along with I'm sure many others, keeping state within the DOM has fallen out of favor of more comprehensible state management inside of JS (like React Hooks, Redux...etc.)

What is the current use-case for jQuery? I'm curious from hearing it's current users answer this.

Re: jQuery 3.6.0

#7
JQuery and reading Resig's book and viewing the source code are responsible for lifting me from horrible dev to below average dev:-)

I learned to extend the library and understood to create some minimal libraries for myself.

It can be very useful to this day and is almost a ballerina when comparing the bloat of other frameworks or library stacks.

You never know maybe the come up with something better than react.

Re: jQuery 3.6.0

#8
jQuery taught me how to write JavaScript frameworks. John Resig, the founder of jQuery, wrote a book called "Secrets of the JavaScript Ninja" was back then really a mindbender.

Function.prototype.toString() is really the craziest thing I know to date regarding JS. Heavily used in earlier versions of jQuery according to the book.

Re: jQuery 3.6.0

#9
post #6

Do people still use jQuery? I thought the biggest advantage of this library back in the day was css selector access of DOM nodes (back when we only had getElementById, getElementsByClassName, and getElementsByTagName). This has been rolled into the Javascript document api via document.querySelector, and document.querySelectorAll. Also there are browser compatibility issues that jQuery solved but a lot of these are so…

Legacy systems, probably.

I read, Ember.js would depend on it.

Re: jQuery 3.6.0

#10
Crazy to think what legacy jQuery and others left. Now I am using React and the usual lib stack.

But I remember using jQuery, pug (or jade), browserify, bower... that was what 5 to 6 years ago?

Post reply on HN