5 ms·

does using jQuery today make things easier to maintain? i am not so sure. you don't even need jQuery for many things today that you would have used it for thank

does using jQuery today make things easier to maintain? i am not so sure. you don't even need jQuery for many things today that you would have used it for thanks to improvements in the Web API, CSS, and JS. also, maintainability of dependencies in web projects that do use build chains seems much better today than even 8 years ago, and it seems to be improving. esbuild, vite, and other projects have simplified the tool chain. improvements in CSS have reduced the need for pre-processors, etc.

ivape 1y ago
It's still a better api than the native document.query stuff that they put into the browsers. It puts so many api developers to shame. It's a masterclass. React still cannot figure out a plugin.
- someothherguyy 1y ago
  I developed with jQuery for nearly a decade and I would disagree. No one who argues for this seems to remember the mess of jQuery dependencies in the form plugins people would include in projects, before HTTP/2, just to have some simple functionality like a carousel, transitions, submitting forms with AJAX (XHR), and so on. Many of those things are a few lines of code now, where they were sometimes hundreds of lines of code in the past when people developed this way. The prototype pollution and general undefined behavior introduced by plugins was nearly impossible to track in projects where teams were plugin hungry. Additionally, the spaghetti that existed where people would interweave on element event attributes (onclick, etc) with scripts lead to huge headaches debugging events before devtools in browsers was mature as it is today. Honestly, I could go on forever. Walk into a large project that is 15 years old and still using jQuery UI, and you might change your mind on the merit of its elegance. jQuery was one of the nicest things around at a time when it was needed, but pining for this version of the past boggles my mind.
  - ivape 1y ago
    Jquery developers were just uneducated on structure. That's why the code was spaghetti. I would say your average Jquery developer didn't even know how to structure a well defined singleton: App = { } People are a lot more educated now. But you're right, we can't go backward, but there are many good things about Jquery that were mostly thrown out by Angular and React, and I think there's a middle-ground here somewhere. Anyways, not like it matters, AI has arrived.
    - deleted 1y ago
      [deleted]
- const_cast 1y ago
  Right, it's unfathomable that we ended up with the ridiculously verbose query API. When jquery is right there. Just steal that API. That's what C++ has been doing with boost for, like, 20 years.

ivape 1y ago

It's still a better api than the native document.query stuff that they put into the browsers. It puts so many api developers to shame. It's a masterclass. React still cannot figure out a plugin.

someothherguyy 1y ago
I developed with jQuery for nearly a decade and I would disagree. No one who argues for this seems to remember the mess of jQuery dependencies in the form plugins people would include in projects, before HTTP/2, just to have some simple functionality like a carousel, transitions, submitting forms with AJAX (XHR), and so on. Many of those things are a few lines of code now, where they were sometimes hundreds of lines of code in the past when people developed this way. The prototype pollution and general undefined behavior introduced by plugins was nearly impossible to track in projects where teams were plugin hungry. Additionally, the spaghetti that existed where people would interweave on element event attributes (onclick, etc) with scripts lead to huge headaches debugging events before devtools in browsers was mature as it is today. Honestly, I could go on forever. Walk into a large project that is 15 years old and still using jQuery UI, and you might change your mind on the merit of its elegance. jQuery was one of the nicest things around at a time when it was needed, but pining for this version of the past boggles my mind.
- ivape 1y ago
  Jquery developers were just uneducated on structure. That's why the code was spaghetti. I would say your average Jquery developer didn't even know how to structure a well defined singleton: App = { } People are a lot more educated now. But you're right, we can't go backward, but there are many good things about Jquery that were mostly thrown out by Angular and React, and I think there's a middle-ground here somewhere. Anyways, not like it matters, AI has arrived.
  - deleted 1y ago
    [deleted]
const_cast 1y ago
Right, it's unfathomable that we ended up with the ridiculously verbose query API. When jquery is right there. Just steal that API. That's what C++ has been doing with boost for, like, 20 years.