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

React is the new jQuery

bradfrost.com

Post reply on HN
Print view View original

101–110 of 206 posts

Re: React is the new jQuery

#101

Post by anthonybullard »

pankajdoharey wrote: post #51
joelhooks wrote: post #50

Earlier quoted context omitted.

This just isn’t true. React has been going strong for 4 years with no sign of slowing down.

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.

Actually the product that makes Google the vast majority of it's money is written in the Dart variety of Angular(AdWords)

Reference: https://youtu.be/-HUHRRYQl5k?t=2m4s

Re: React is the new jQuery

#102

Post by TomK32 »

superfrank wrote: post #13

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

Hey, those young kids just don't know how frontend development was before jQuery.

Re: React is the new jQuery

#103

Post by hrktb »

alfredxing wrote: post #81
superfrank wrote: post #13

> 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 agree jQuery was very useful early on, especially since it abstracted cross-browser differences and APIs. However in my experience, a couple of things were key to creating a negative view of jQuery: 1. Security and unsafe defaults, for example: evaluating remote JavaScript by default [1]; and unsafe DOM parsing by default [2] 2. Not really to blame on jQuery, but its ease of use for DOM manipulation led to programm…

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

Times were different

Re: React is the new jQuery

#104

Post by eropple »

superfrank wrote: post #59
danShumway wrote: post #32

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…

> 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. That's fair. > The other comparative downside of JQuery was that components started to rely on it as a shared library, which meant developers suddenly needed to do dependency management. That is (usually) a bad idea. React absolutely do…

> Who is going to want to use a dropdown component that has the entire React 15.3 lib bundled into it?

...Nobody? Which is why peer dependencies exist.

NPM/Yarn aren't perfect by any stretch, but maybe mind Chesterton's Fence and refrain from reflexively assuming the developers of them are idiots?

Re: React is the new jQuery

#105

Post by UlisesAC4 »

djsumdog wrote: post #83

I really like the linked Vue/Jquery article in the story as well. I've built some stuff in Vue and I really like it. It can be incredibly simple. I'm not a huge fan of React. I'm really not a fan of any site that requires Javascript to view. If it's a new article and I get a blank page, I immediately stick it in archive.is. I'm not turning on Javascript for your site just to view content. Fuck that. Fix your site to…

When javascript Is disabled you just loose the pwa features, pages are full loaded as html.

For SSR you are sending the HTML text instead of JSON. Time ago you needed nodejs for SSR I do not know the alternatives today.

Re: React is the new jQuery

#106

Post by [deleted] »

paulddraper wrote: post #7
steve_adams_86 wrote: post #5

Earlier quoted context omitted.

You also get convention. jQuery didn't offer much of that once you started gluing its functions together... I can usually jump into someone's react code and get what's going on pretty quickly unless they did something really gnarly with incredibly nested props. Even then, at least I still know where to drill down. With jQuery soup, you didn't get that luxury. Being able to have an entire team know how to build compon…

jQuery had a lot of convention, for both it and it's plugins. jQuery + co. have very consistent "look and feel"

[deleted]

Re: React is the new jQuery

#107

Post by bigbadgoose »

> I’m still struggling to comprehend why so many organizations are so eager to take the sturdy, foundational layer of the frontend stack and rewrite it all in a proprietary format.

it's about workforce and durability of the platform

Re: React is the new jQuery

#108

Post by pbowyer »

threatofrain wrote: post #15
statictype wrote: post #9

If you tear out something like jQuery, you’re going to have to figure out a way to get those accordions to expand and collapse again. If you tear out React, you get a blank page. React is a big commitment. This is probably the only real concern I see. jQuery is a library for DOM manipulation. It can co-exist with many other libraries. React is an entire framework. These days you need jquery less because browsers are…

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 was https://reactjs.org/docs/add-react-to-an-existing-app.html, which reads like it would make sense to an xperienced React developer, but not someone coming new to it.

Re: React is the new jQuery

#110

Post by pbowyer »

rbosinger wrote: post #76

As a member of a busy, small team with a Rails app and a jQuery heavy front-end... I agree. We use React in a few places and wanted to simply introduce it slowly and "convert to React where we could". It simply has not worked out for us. We have typical server side rendered HTML that has been progressively enhanced with sprinkles of JS (jQuery + various plugins). We do not and cannot book much developer time for refa…

Thanks for sharing, this is exactly what I am considering doing at the moment.

Any thoughts on https://news.ycombinator.com/item?id=17213264?

Post reply on HN