Live data from Hacker News

React is the new jQuery

bradfrost.com

131–140 of 206 posts

Re: React is the new jQuery

#131

> React is the new jQuery Anyone who uses "the new jQuery" as some sort of insult (as it seems Sara did in her tweet) probably hasn't been a developer for more than a few years or is just trying to sound smarter than they are by bashing an easy target. The reason jQuery got so popular is that it made common tasks so much easier than anything else at the time. Anyone who was doing web development before jQuery knows w…

Is jQuery unnecessary because the functionality is built into js now? Or browsers? Or other libraries? If it's libraries, are those libraries providing a superset of jQuery or are they just better?

Yes, the DOM API's have greatly improved and are well-supported among browsers now, so jQuery is no longer needed for that. React doesn't solve the problem of inconsistent and unwieldy browser API's (which isn't a problem any more), but of a clean architecture for web applications.

Re: React is the new jQuery

#132

I think there is some confusion comparing jquery with frameworks in general heh- time for a history lesson! So back in the mid-aughts right before jquery there was prototype. I got hired into a job where I had to maintain sites written with both in the past and they were very similar to each other. Ajax was new and so was the class based handling of JS to make it more object oriented. It could be done but prototype m…

To be fair, the things we create today are often far more complex or at least are done in far less time than back then.

Re: React is the new jQuery

#133
post #77

Earlier quoted context omitted.

Curious are you writing newer style javascript with polyfills or just plain old school javascript?

Es2018 all the way. Web workers, classes, Isomorphic code, generators, async await, etc with a splash of Babel Devs have never been happier. Everything just works and online documentation is Rich and plentiful. Plus as I said, core logic works on both server and client and we have offline support as an added bonus.

No bundle but you use Babel? How does that work?

Re: React is the new jQuery

#134

Earlier quoted context omitted.

What does "an entire framework" mean? Because you can just make React the little news and weather widget in the corner of your app / website, as the only React component. Same with Vue. The people for whom ripping out React or Vue leads to a blank page are those who wanted an app from the ground-up. If anything, React is losing because it doesn't include enough out of the box. If you wanted to build a news widget, fi…

> What does "an entire framework" mean? Because you can just make React the little news and weather widget in the corner of your app / website, as the only React component. Same with Vue. Is there a step-by-step tutorial for this? I was googling for one yesterday, because I have a legacy app and want to start moving small components (like datagrids) out of server-side rendering and into components. The best I found w…

Do you find it difficult because it suggests you need to deal with JS modules and building? After you get your tooling setup, you can just include a node in your DOM that React will target and mutate.

Re: React is the new jQuery

#135
I am learning to code and a newbe.

I think jQuery != react.

I do not understand, why experienced people like to compare jQuery with react when both the lib have different goal ? And show that jQuery is bad.

React can be used with jQuery for DOM manipulation. Described in react doc (https://reactjs.org/docs/integrating-with-other-libraries.ht...).

Shall I learn jQuery at all ? Please, guide me.

Re: React is the new jQuery

#136

> React is the new jQuery Anyone who uses "the new jQuery" as some sort of insult (as it seems Sara did in her tweet) probably hasn't been a developer for more than a few years or is just trying to sound smarter than they are by bashing an easy target. The reason jQuery got so popular is that it made common tasks so much easier than anything else at the time. Anyone who was doing web development before jQuery knows w…

> probably hasn't been a developer for more than a few years or is just trying to sound smarter than they are by bashing an easy target. Yet, Sara is neither of those, she's a well respected developer, who's work with CSS and SVG is world-class. If she's using jQuery as a comparison she's doing it from a place of experience and knowledge

Who is? CSS and SVG are great, but how is her javascript? Neglecting the role that jQuery played is foolish, and even respected developers can say foolish things now and then.

Re: React is the new jQuery

#137

Earlier quoted context omitted.

>cant even name a similar piece of software in web development history that is as important as jQuery. Php?

Nah, there were always tons of alternatives to PHP. What real alternatives were there to jQuery? There were none.

I know this is a rhetorical question, but Prototype.js was pretty similar to jQuery; although jQuery won the popularity contest.

Re: React is the new jQuery

#140

> React is the new jQuery Anyone who uses "the new jQuery" as some sort of insult (as it seems Sara did in her tweet) probably hasn't been a developer for more than a few years or is just trying to sound smarter than they are by bashing an easy target. The reason jQuery got so popular is that it made common tasks so much easier than anything else at the time. Anyone who was doing web development before jQuery knows w…

I don't think JQuery ever got bad. It just got unnecessary, like you said. But it took a lot of work to convince people that it was unnecessary. A charitable explanation of Sara's tweet might be that, like with jQuery, it is becoming difficult to convince new developers that React may not be necessary for their next project. The other comparative downside of JQuery was that components started to rely on it as a share…

> But it took a lot of work to convince people that it [JQuery] was unnecessary.

First it took about a decade of browser and ECMA very intensive development to actually make it unnecessary.

> it is becoming difficult to convince new developers that React may not be necessary for their next project.

Give it a decade for the web "components" to actually become composable and for inventive and useful native language built-in solutions to state management to happen before you start advocating people out of React. Until then telling people they might not need React is not a step forward but backward. Imagine people saying "you might not need jQuery" in times where IE reigned and browsers were wildly incompatible.

Post reply on HN