Live data from Hacker News

jQuery 4

blog.jquery.com

251–260 of 313 posts

Re: jQuery 4

#251

Related: This is a nice write-up of how to write reactive jQuery. It's presented as an alternative to jQuery spaghetti code, in the context of being in a legacy codebase where you might not have access to newer frameworks. https://css-tricks.com/reactive-jquery-for-spaghetti-fied-le...

But if you do that, you'll also find it easy to write plain JS without any libraries or frameworks. document.querySelectorAll is just slightly more verbose than $(). I have personally done this: for simple web pages, I just eschew all dependencies and write plain JS.

Re: jQuery 4

#252
post #15

Still one of my favourite libs on the whole planet. I will always love jQuery. It is responsible for my career in (real) companies. Live on jQuery! Go forth and multiply!

I love tech hype cycles haha, I remember when you got laughed at for using jquery and now it seems everyone’s burned out and happy to go back to a simpler time

Haha, I remember that very clearly. Remember this?:

https://stackoverflow.com/questions/2826791/am-i-using-too-m...

Re: jQuery 4

#253

Earlier quoted context omitted.

It is still used by many websites.

Indeed. Though a lot of its feature found their way into plain vanilla Javascript and browsers, the syntax is still so much easier with jQuery.

The clean and simple syntax was always the reason to use jQuery. I remember seeing sites that were anti-JQ, so they'd show how you could replace a single jQuery line with 9 vanilla JS lines and uh... somehow this would improve things?

I can't believe how much public opinion has changed over the years. Love it, actually.

Re: jQuery 4

#254
post #94

Earlier quoted context omitted.

The problem with React is that it solved frontend. So the options are to 1. Code React all day and be happy with it. 2. Come up with reasons why it's bad. There are many talented and intellectually curious people in the field which lean towards 2.

It didn't solve frontend, it sold developers one lie (i.e. ui = f(state) ) and managers another (developers are interchangeable gears). Problems are only truly solved by the folks who dedicate themselves to understanding the problem, that is: the folks working on web standards and the other folks implementing them.

Too bad the problems getting solved aren't the problems that need solving. Maybe this is one of the reasons software development is such a joke of a profession.

Re: jQuery 4

#256

For the record, JQuery is NOT to blame for the so called spaghetti code. Most people seem to blame JQuery for their own short coming. Most people also do not seem to understand the genius that was contained in JQuery. See " http://eyeandtea.com/crxcmp " for an example of what could already be done with JQuery in the IE8 era. A lot of the things later invented in the browser were to mask these shortcomings instead of…

sdl is still alive and kicking, doesn't seem looking ground to new replacements?

Re: jQuery 4

#257
post #30

Earlier quoted context omitted.

WordPress ships with 3.x and is already looking to update to 4

I was talking about a lot of sites in wordpress, not Wordpress themselves

If people haven't updated their sites in 10+ years, that's their problem. Has nothing to do with wordpress or jQuery

Re: jQuery 4

#258

For the record, JQuery is NOT to blame for the so called spaghetti code. Most people seem to blame JQuery for their own short coming. Most people also do not seem to understand the genius that was contained in JQuery. See " http://eyeandtea.com/crxcmp " for an example of what could already be done with JQuery in the IE8 era. A lot of the things later invented in the browser were to mask these shortcomings instead of…

Wait, SDL is no longer relevant? What is the alternative?

Re: jQuery 4

#259

Earlier quoted context omitted.

Zepto! That's a name I haven't heard in years. I don't remember how it happened but I'm still a member of the ZeptoJS org on Github.

I really like that project! Why don't y'all hand it over to someone willing to do maintenance or at least archive it?

Who wants to do maintenance? Open an issue.

Re: jQuery 4

#260
post #228

Earlier quoted context omitted.

> I kid you not, there were 30+ redux actions chaining in the most incomprehensible ways I 100% believe this, as it describes all the redux codebases I've seen. The library seems to be an antipattern of indirection.

This sounds like an engineering quality problem rather than a tooling problem. Well structured redux (or mobx or zustand for that matter) can be highly maintainable & performant, in comparison to a codebase with poorly thought out useState calls littered everywhere and deep levels of prop drilling. Redux Toolkit has been a nice batteries-included way to use redux for a while now https://redux-toolkit.js.org/ But the…

I took a look at the quickstart guide at https://redux-toolkit.js.org/tutorials/quick-start and to me it still seems to add a lot of indirection.
Post reply on HN