Live data from Hacker News

React is the new jQuery

bradfrost.com

171–180 of 206 posts

Re: React is the new jQuery

#171
post #156

Earlier quoted context omitted.

I dont disagree, React has some solid underpinnings but for now VUE has some momentum, till the next one comes along. Google gave up on the idea long back. Google develops Angular but doesnt use it in any of their core products. They themselves use Google Closure library for gmail or word processor.

Isn't the new YouTube website running Angular? Please don't shoot me if I'm wrong, I don't have any citations, I just presumed (on phone, too lazy to look up).

Not according to Augery (angular chrome extension), but not sure if all evidence can be built out of the result.

However, mobile.twitter.com and facebook proper are using react. Along with Walmart.com and many, many others.

The biggest Angular app I've seen is probably grubhub, and there's some painful state bugs there... in fact I don't think I've ever seen an angular app (not using rxjs or redux) that doesn't have weird state management bugs.

Re: React is the new jQuery

#172
post #145

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.

The comparison Sara made was that React can be overused just as jQuery was. The problems with jQuery is that it's mostly a set of functions to simplify Ajax and DOM manipulation so it's not really helpful for the structure of an application. React (and other frameworks surch as Angular, Ember and Vue), on the other hand, helps you to build reusable component which helps a lot to scale. Also jQuery's golden age was wh…

My only advice to people today would be to use one of the much smaller jquery-like libraries for DOM interaction/events and fetch (shimming ie11) instead of other wrappers.

Re: React is the new jQuery

#173

vue seem to be an evolution of react and angular. it is as if some react developer sat down and said, “how can we make this even simpler so that even my grandson can do it.” i appreciate when we have guys like the authors of Vue come forward driving the community and taking web development to the next level giving us a more elegant solution.

More like a cousin... I see Vue as a nice component system for smaller applications, I don't think I'd want to build anything of even moderate complexity with it.

React is for building applications, especially with teams. Combined with redux and a handful of other pieces, it's very nice.

Angular, I don't get why anyone would choose it today (I've said it time and again).

Re: React is the new jQuery

#174
post #150

Since early in my career when hiring I've found developers who only know 'jQuery / Angular / Vue / React' but not the underlying Javascript, I swear "x is the new y" is said every time a new framework gets 6 months into vogue.

>Since early in my career when hiring I've found developers who only know 'jQuery / Angular / Vue / React' but not the underlying Javascript

It's frightening, the degree to which many professional web app developers do not know the fundamentals of Javascript. Our technical interview starts out with ridiculously simple questions and gets progressively more difficult and esoteric. And a dismayingly high number of candidates don't get past the first couple of questions. And these are people with years of experience and at least some of the hot JS frameworks on their resume.

Re: React is the new jQuery

#175
post #156

Earlier quoted context omitted.

Isn't the new YouTube website running Angular? Please don't shoot me if I'm wrong, I don't have any citations, I just presumed (on phone, too lazy to look up).

Not according to Augery (angular chrome extension), but not sure if all evidence can be built out of the result. However, mobile.twitter.com and facebook proper are using react. Along with Walmart.com and many, many others. The biggest Angular app I've seen is probably grubhub, and there's some painful state bugs there... in fact I don't think I've ever seen an angular app (not using rxjs or redux) that doesn't have…

I tried using Angular 1 when it came out and it seemed like too much work to learn for such a small benefit. I started learning React at the start of last year and have found it phenomenal. I am not comparing the two, let alone arguing in favour of Angular. I just thought with the swap to Material Design (and async loading data and components) in YouTube, that they were using Angular. Your opinion about YouTube using Angular (or not) has more citation and authority than mine, so I will assume in the future that YouTube does not use Angular (without certainty, of course).

Re: React is the new jQuery

#176

Vue is for enhancing web pages.. you can do applications, but they get very complex beyond small-mid sized apps. React is made for building web-based applications. You can do small stuff with it, but it's often overkill. Just because you can use a butter knife to turn a flathead screw, doesn't mean it's the right tool for the job. These days I might reach for Vue as a jQuery stand-in, but more likely, I'd use a small…

Vue can be used to enhance web pages, but it works equally well if you want to build a large application. This was one of the design goals. Something that you can start small and scale up with that works equally well for both. If you use the Vue CLI you can have a setup with a router and build tools and setup something very similar to create react app.

Re: React is the new jQuery

#177
post #103

Earlier quoted context omitted.

To be fair, when jQuery was growing up PHP with magic auto global variables was the fury. Times were different

I think by 2006 magic auto globals was already off by default (4.2, which was released in 2002, was the one that turned it off, and though 4.2 was still widely used by the time jQuery came about, register_globals was considered bad practice in general by at least 2004, if not even earlier).

good point. Your timeline is accurate, and while PHP installs tend to be out of date and people following tutorials would just turn off security features, by 2006 the trend should have been in decline, yes.

More than anything, the crazy thing for me is that jQuery seemed to have been there from the wake of the web, when it came out only one year before the iPhone.

Re: React is the new jQuery

#178

Earlier quoted context omitted.

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…

Being used to jQuery, I really see no reason not to use it in new projects. I could learn all the new native equivalents, and even then still ending up doing more work than if I'd been using jQuery, just to save a little bit of page load time and filesize, but it would almost certainly not be worth it.

Indeed. I occasionally write a webbased tool to deal with a specific task (say formatting some form of codec data, or a simple dashboard for a specific event, or a small config generator, or whatever), userbase is in the I could learn and use $latest_thing, and maybe it would be great. That will triple the time taken to develop, but whatever. However in a couple of years time when I come to need to write something else, $latest_thing will be old hat, and replaced by $shiny_and_new. Rather than having 10 years of nice simple code based on jquery, I get some based on Angular, some on React, some on Vue, some on Meteor, or whatever.

I'm not a programmer, I'm not a wireman, and I'm not a carpenter. I program in the same way I'll run a network cable or get a screwdriver out, it's a tool I can use to solve a specific task. I like tools that are the same, year in, year out.

That's not to say the latest frameworks aren't all great, if you're building something for a million users and want to take advantage of shiny new features that's great, but for those that aren't, there's still a place for boring old things in a large part of the computer industry.

Re: React is the new jQuery

#179

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

Yes that's really a great way of seeing it. Jquery kind of graduated to obsolescence as many of its useful features made it into core JS.

When querySelector and ES6 came about, I found myself not needing jquery by default.

Re: React is the new jQuery

#180

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

Agreed. Furthermore, a lot of those tasks were downright unnecessarily painful and tedious time sinks, e.g. browser agnostic control when the ecosystem was much more fragmented and HTML5 more nascent. Also, jQuery's documentation was solid, and it was very easily extensible.
Post reply on HN