Ask HN: Is jQuery still a thing?
41–50 of 90 posts
Re: Ask HN: Is jQuery still a thing?
#42Every other framework relies on JQuery so--yes, absolutely--it's still a thing. And if you don't work for a company that is in the JavaScript-framework-of-the-month mode, you should know JQuery is still king.
No popular current generation framework relies on jQuery. The most recent one I can come up with is Angular 1's reliance on their jQlite micro-library but would use the full jQuery if it was on the page.
Re: Ask HN: Is jQuery still a thing?
#432.3 million downloads in the last month and 4883 dependencies... what do you think?
Re: Ask HN: Is jQuery still a thing?
#44If you're writing more than a couple hundred lines of javascript, the jQuery model of putting your application state in the DOM is inferior to pretty much any other application model. There's a reason everybody went to Backbone and then to the component libraries. Separating your model and rendering concerns and delegating the latter to your framework roughly halves the amount of code you need to write.
Re: Ask HN: Is jQuery still a thing?
#45Yes, jQuery is good and most people still use it. It does its job perfectly fine. The thing is, HN is a very small like-minded community of people who are always looking for something better than the status quo, which is why you're always seeing news about things like React and Vue, etc.
Re: Ask HN: Is jQuery still a thing?
#46Every other framework relies on JQuery so--yes, absolutely--it's still a thing. And if you don't work for a company that is in the JavaScript-framework-of-the-month mode, you should know JQuery is still king.
> Every other framework relies on JQuery This just isn't true. OP mentioned React, Vue.js, and Mithril. None of these use jQuery as a dependency. Neither does Angular, Backbone, or Ember.js.
That being said, I don't think knowing jQuery is very valuable for JS developers anymore. Browser standards have come a long way and frameworks are handling your DOM writes for you, so that major use case for jQuery is gone in any website that requires substantial scripting.
Re: Ask HN: Is jQuery still a thing?
#47Absolutely. Most projects that would be considered "websites" rather than "web applications" are likely candidates for jQuery. It's still extraordinarily useful.
Pick the right technology to solve the problem you're trying to solve.
Some inexperienced devs just try and cram every single technology they've ever heard of into a simple project when it's not needed. You're not at Facebook's scale just yet where many of these abstractions are anything other than an extra complication and a waste of time and future liability.
Your average simple website for a law firm, bike repair shop, or a pizza delivery place doesn't need 93 different libraries/frameworks/technologies/build systems/etc to show/hide a couple products or submit a form or two. You can go pretty far with just jQuery in many cases.
It gets a little more complicated as you go from simple site to more complex site to app to more complex app, but I see too many developers trying to be trendy and over engineering simple problems and wasting a lot of time and money.
Re: Ask HN: Is jQuery still a thing?
#48Earlier quoted context omitted.
PHP is some tool that was never really good, but had some compelling features that no other tools provided. Except that now there are better tools for any task it solved, excluding the task of "maintaining a PHP codebase". If you are starting a new project on it, you should indeed feel silly.
I disagree. Let's try adding 0.2 and 0.3 with the JScript library of your choosing and see if it's any easier than PHP.
Re: Ask HN: Is jQuery still a thing?
#49The only use case for jQuery is if you want virtually all your logic and rendering to be server side and only want to use javascript for toggles, form checking, or other jQuery sprinkles. I wouldn't choose this but if someone did and picked jQuery I wouldn't question the jQuery part much. If you're writing more than a couple hundred lines of javascript, the jQuery model of putting your application state in the DOM is…