Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Is jQuery still a thing?

news.ycombinator.com

Post reply on HN
Print view View original

61–70 of 90 posts

Re: Ask HN: Is jQuery still a thing?

#61

Post by jorgthuijls »

grayrest wrote: post #57
Raed667 wrote: post #42

Earlier quoted context omitted.

OpenUI5 [0] relies on jQuery [0] http://openui5.org/

I'd never heard of this library and I spend a couple hours a day reading developer news so I wouldn't call this popular. I'd also argue that this as a current generation framework. I only did a brief skim but the patterns remind me of a Knockout or Enyo codebase with data binding between components doing explicit dom manipulation. The contributors tab shows a 2014 start but I'd have guessed a 2010-2011 start from loo…

You'd be surprised. UI5 is made by SAP as their go-to UI technology. SAP's profit last year was over 6B euro and it's used in almost every large enterprise out there. It's just hard to see as a tech company because it's not consumer facing.

I'm an SAP and UI5 developer.

Re: Ask HN: Is jQuery still a thing?

#62

Post by carsongross »

Of course it is!

The way I build web apps is to use intercooler.js (which is built on top of jQuery) for my AJAX and then jQuery, or jQuery-based plugins, for UI needs.

Works great. Yes, the jQuery API has some aspects that haven't aged all that well, but it's a pretty well thought out and through library that provides great tools that should have been baked into all browser environments since the start, and that has a rich ecosystem around it to boot.

The jQuery haters are usually folks who tried to write an SPA with it, which they say, correctly, is a terrible idea. But then, building an SPA is usually a terrible idea as well.

Re: Ask HN: Is jQuery still a thing?

#63

Post by kafkaesq »

tomcam wrote: post #13

Do you know a better library for support of a wide array of browsers going back many years, with a huge log of support issues and test cases behind it?

And drop-dead simple, so that a programmer from any background can pretty much just look at the code, and figure it out?

Re: Ask HN: Is jQuery still a thing?

#64

Post by drinchev »

dabernathy89 wrote: post #7

Absolutely. Most projects that would be considered "websites" rather than "web applications" are likely candidates for jQuery. It's still extraordinarily useful.

I disagree. jQuery was the tool that acts as a "polyfill" for cross-browser compatibility. Nowadays jQuery is dying, not because of React, Angular or TypeScript, Elm. It's dying because of browser-support of `querySelectorAll`, unified event handlers, unified AJAX request API and others.

jQuery had it's time. Now you just use "vanilla" JS and it is enough. No external dependencies for your landing-page / non-web-app site.

Re: Ask HN: Is jQuery still a thing?

#65

Post by commentzorro »

carsongross wrote: post #62

Of course it is! The way I build web apps is to use intercooler.js (which is built on top of jQuery) for my AJAX and then jQuery, or jQuery-based plugins, for UI needs. Works great. Yes, the jQuery API has some aspects that haven't aged all that well, but it's a pretty well thought out and through library that provides great tools that should have been baked into all browser environments since the start, and that has…

> But then, building an SPA is usually a terrible idea as well.

Would you care to elaborate on this? I'm interested in why.

Re: Ask HN: Is jQuery still a thing?

#66

Post by carsongross »

commentzorro wrote: post #65
carsongross wrote: post #62

Of course it is! The way I build web apps is to use intercooler.js (which is built on top of jQuery) for my AJAX and then jQuery, or jQuery-based plugins, for UI needs. Works great. Yes, the jQuery API has some aspects that haven't aged all that well, but it's a pretty well thought out and through library that provides great tools that should have been baked into all browser environments since the start, and that has…

> But then, building an SPA is usually a terrible idea as well. Would you care to elaborate on this? I'm interested in why.

I was obviously being flippant, but a long story short is that going to a JSON-based, RPC-style SPA app gives up a lot of the advantages of the original RESTful web network architecture, not the least of which being simplicity.

Long-suffering HN readers can skip all of this (sorry guys) but I expand on this in the following blog posts:

http://intercoolerjs.org/2016/01/18/rescuing-rest.html

http://intercoolerjs.org/2016/02/17/api-churn-vs-security.ht...

http://intercoolerjs.org/2016/05/08/hatoeas-is-for-humans.ht...

Re: Ask HN: Is jQuery still a thing?

#67

Post by pragmatic »

Yes.

1. There are some edge cases where it is still useful and it would be way more painful to reimplement it in vanilla js (though maybe still possible). But in these edge cases why bother when:

2. In any largish project invariably _something_ will require jquery. Think Bootstrap or some widget library the boss/users absolutely want or something some "UI" person built themselves.

Re: Ask HN: Is jQuery still a thing?

#68

Post by commentzorro »

carsongross wrote: post #66
commentzorro wrote: post #65

Earlier quoted context omitted.

> But then, building an SPA is usually a terrible idea as well. Would you care to elaborate on this? I'm interested in why.

I was obviously being flippant, but a long story short is that going to a JSON-based, RPC-style SPA app gives up a lot of the advantages of the original RESTful web network architecture, not the least of which being simplicity. Long-suffering HN readers can skip all of this (sorry guys) but I expand on this in the following blog posts: http://intercoolerjs.org/2016/01/18/rescuing-rest.html http://intercoolerjs.org/20…

All of these seem to imply discoverability and queries are the biggest pain point in web apps. For me, in creating specific purpose business apps, the biggest headaches are presenting the data in ways that minimize the user's unnecessary actions and, even more of a pain, wiring things up so an event in one location triggers the proper client display changes in another location.

For my use cases, discoverability and ad hoc queries just don't apply.

Re: Ask HN: Is jQuery still a thing?

#69

Post by gremlinsinc »

Rumudiez wrote: post #46
georgedrummond wrote: post #32

Earlier quoted context omitted.

> 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.

Angular 1.x uses a version of JQ Lite, and will utilize jQuery if it's already loaded on the page. 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.

Really? what if you have to support legacy apps that are 100% jquery on the frontend / php on the back? It's VERY much still a thing..

Re: Ask HN: Is jQuery still a thing?

#70

Post by gremlinsinc »

marcosdumay wrote: post #26
toadkicker wrote: post #15

Earlier quoted context omitted.

It's really silly that is how the culture behaves. The right tool for the job is a common moniker in other industries, yet in ours its the source of heated debate and hipsterdom.

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, -- sure if you're building native php apps w/out a framework.. but Laravel is probably the easiest MVC framework out there to pickup and build something that works super fast without having to know how to deploy a VPS, etc... For small to midsize php is STILL a workhorse -- but I wouldn't recommend wordpress or vanilla php themselves.

Laravel collections alone make it almost a functional language when using it w/ laravel.

Post reply on HN