undefined | Better HN

0 pointsEspressoGPT2y ago0 comments

Why the heck would you use jQuery in 2023 though?

0 comments

Because it’s much cleaner, readable code than anything created since.

It's a boring and battle proven tool that just works and has no use by date, by the way.

It has. The issue jQuery was designed to solve doesn't exist anymore, hence there's no reason to rely on this heavy and convoluted library any longer. There really are better solutions.

varispeed2y ago

What do you mean the issue doesn't exist?

nprateem2y ago

My main use case will be basic UI interaction, mostly just posting or fetching data from a backend then updating the innerHTML on some element. Vanilla might be enough, but I'm keeping my options open.

Also, no compilation step, so no need for npm, etc

maxboone2y ago

IMO that's where alpine.js complements HTMX, you can use HTMX mainly for interfacing with a server and then use alpine.js for any special interaction that does not require a round-trip with the server.

bardak2y ago

That's my thought as well. Anything that needs new data from the server uses HTMX and if you need to manipulate something already on the page use Alpine, Jquery, vanillajs, or whatever other framework you prefer.

rodorgas2y ago

JQuery would make sense when we didn’t have querySelector and fetch API. I can’t think of any reason to use it today on a new project, there are not advantages over vanilla.

tambourine_man2y ago

The native API is much more verbose and less composable. It was a real lost opportunity.

1 more reply

synergy202y ago

jQuery's syntax is 10x better than vanilla javascript

1 more reply

EspressoGPTOP2y ago

I'd strongly suggest using something like ArrowJS instead of jQuery for that.

j / k navigate · click thread line to collapse

0 comments

tambourine_man2y ago

Because it’s much cleaner, readable code than anything created since.

varispeed2y ago

It's a boring and battle proven tool that just works and has no use by date, by the way.

EspressoGPTOP2y ago

It has. The issue jQuery was designed to solve doesn't exist anymore, hence there's no reason to rely on this heavy and convoluted library any longer. There really are better solutions.

varispeed2y ago

What do you mean the issue doesn't exist?

nprateem2y ago

Also, no compilation step, so no need for npm, etc

maxboone2y ago

bardak2y ago

rodorgas2y ago

JQuery would make sense when we didn’t have querySelector and fetch API. I can’t think of any reason to use it today on a new project, there are not advantages over vanilla.

tambourine_man2y ago

The native API is much more verbose and less composable. It was a real lost opportunity.

1 more reply

synergy202y ago

jQuery's syntax is 10x better than vanilla javascript

1 more reply

EspressoGPTOP2y ago

I'd strongly suggest using something like ArrowJS instead of jQuery for that.

j / k navigate · click thread line to collapse