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

React Makes You Sad?

github.com

Post reply on HN
Print view View original

151–160 of 211 posts

Re: React Makes You Sad?

#151

Post by qudat »

SonicSoul wrote: post #135
et1337 wrote: post #30

This reminds me of that Netflix talk on React [1]. In it, the guy first praises React to the heavens, then spends the rest of the session explaining all the ways they had to disable and work around React to get what they wanted with decent performance. It seemed to me like their use case could have been done with jQuery in a few hundred lines. Maybe I missed something. [1] https://www.youtube.com/watch?v=g01dGsKbXOk

just curious how you arrived at jQuery comparison. isn't that just a library for DOM utilities while react is a view engine optimized for minimum dom manipulation using observable pattern?

jQuery and React are DOM manipulation libraries. jQuery packaged a bunch of other stuff in it but at its core it is all about DOM manipulation.

Re: React Makes You Sad?

#152

Post by qudat »

SonicSoul wrote: post #135
et1337 wrote: post #30

This reminds me of that Netflix talk on React [1]. In it, the guy first praises React to the heavens, then spends the rest of the session explaining all the ways they had to disable and work around React to get what they wanted with decent performance. It seemed to me like their use case could have been done with jQuery in a few hundred lines. Maybe I missed something. [1] https://www.youtube.com/watch?v=g01dGsKbXOk

just curious how you arrived at jQuery comparison. isn't that just a library for DOM utilities while react is a view engine optimized for minimum dom manipulation using observable pattern?

jQuery and React are DOM manipulation libraries. jQuery packaged a bunch of other stuff in it but at its core it is all about DOM manipulation.

Re: React Makes You Sad?

#153

Post by janpieterz »

joelcollinsdc wrote: post #132
jaegerpicker wrote: post #117

Earlier quoted context omitted.

I just went to netflix and it's not at all how you describe. It's incredibly fast and live filters as I type. There may be an abundance of poorly written react apps out there but netflix does not appear to be one.

maybe i'm just typing too fast. I tried "the best marigold" (for the best marigold hotel). I watched the i in marigold disappear from the search box. Deleting the string (by holding down the delete key, the X works just fine) takes forever as well. I'm using chrome if it matters.

Just tested it and didn't find it super bad, but I am honestly (negatively) surprised. It does indeed lag quite a bit and feels very unnatural. Chrome here as well. I use React quite a bit myself and haven't experienced this in my own apps. Odd!

There's also a slightly annoying flicker when you type the last bit and it keeps returning the same movies.

Re: React Makes You Sad?

#154

Post by erichmond »

aidenn0 wrote: post #73

This flowchart assumes you are writing in javascript. Perhaps this is understandable as it's a javascript library, but there are several frameworks for other languages (most notably Om/Clojurescript).

Why in the world is this downvoted? Om/CLJS has some of the nicest bindings for React. It's extremely valid that if you are frustrated with React that you could experiment with the clojurescript ecosystem to see if that would "make you happy".

Re: React Makes You Sad?

#155

Post by tptacek »

dsp1234 wrote: post #21
tptacek wrote: post #12

Earlier quoted context omitted.

This is the weirdest argument I've ever heard against React, and, as someone who does a fair bit of React work, I try to pay attention to all those arguments.

It's certainly a weird phrasing of an argument. However, it seems reasonable that some programmers will not like the specific style of structure that react espouses. Specifically the top-down push of data through parent-child component relationships. Specifically, if you are working with a lot of third party components that are not react based, it can be hard (or a lot of boilerplate) to contain them within react app…

Sorry, that obviously isn't one of my better comments, and other commenters have done a much better job than I did reacting to the original argument.

What I'm objecting to isn't the idea that React's ideas aren't for everyone, or perfect for every application, but rather that React's issues somehow stem from some kind of Facebook-y need for "control". That's an especially weird claim to make given how simple and open-ended React (by itself) is.

Re: React Makes You Sad?

#156

Post by notduncansmith »

Widdershin wrote: post #129
jim-greer wrote: post #110

Earlier quoted context omitted.

That doesn't work if you're trying to build native mobile apps.

Which is a pity. I would love to see something like Electron for mobile.

I'm pretty sure that's exactly what the Cordova project is: https://cordova.apache.org

Re: React Makes You Sad?

#157

Post by tptacek »

kruhft wrote: post #122
kaoD wrote: post #88

Earlier quoted context omitted.

I had the same problem until I saw the light. The problem wasn't React: it was me. You shouldn't merely learn React, but also unidirectional-flow architectures (like Flux, but there are many others, including better ones IMHO). Bidirectional data flow is a pain in the ass and once you understand unidirectional data flow, everything fits much easier. Of course, trying to shoehorn a bidirectional data flow in React is…

Unfortunately I'm not looking for a Religion, I'm just looking to get my job done. Too much structure can be just as bad as not enough when it comes to programming.

It sounds less like you're not open to "religions" and more like you just don't want to be working in React. That's fine; React isn't a moral crusade.

Re: React Makes You Sad?

#158

Post by c0ffe »

Sometime ago, i tried react and found a property named like "do_not_modify_or_you_will_be_fired" (i dont remember in which object).

I understand encapsulation is necessary, but i wonder how feels working with someone who writes code with a shotgun next to him / her.

Re: React Makes You Sad?

#159

Post by nostrademons »

qudat wrote: post #150
vietnameselady1 wrote: post #83

Although I like this a lot, and I think it addresses most individual nuggets of React Sadness in a pretty reasonable way, I am still sad. I am sad because every process rectangle in this chart should also point to a decision diamond that says: "Does it seem that the entire industry has migrated to this stack, whether or not it really makes sense for everyone to? That a feedback loop now influences shops to choose the…

Did anyone claim the same about jQuery a few years ago? First people claim about js library fatigue, now we are complaining about there only being "one employable js library."

Vanilla JS was so horrible when JQuery came out that pretty much everyone loved it, except for a few folks who had been early adopters of Prototype/Mootools/YUI/Ext and were decrying how JQuery didn't have their favorite pet utility function.

I think the JS fatigue we're seeing is because web development is now largely a mature industry. React is roughly the 4th generation of Javascript technologies (1st = DHTML/Layers, 2nd = JQuery/Prototype/Mootools/YUI/Ext/Dojo, 3rd = Angular/Ember/Backbone, 4th = React/Polymer). At this point, there are millions of JS developers, they have seen multiple generations go by, and they just want some stability. The folks who always want to be on the bleeding edge are off doing IoT and VR startups.

IMHO, React is a nice piece of software, but it's a nice piece of software entering a market where existing solutions are already pretty good and much of the action is moving elsewhere. They have to hype it up, because people won't give up their JQuery/Angular/VanillaJS otherwise. It's a very different situation than when JQuery was introduced and web development was recovering from the .com bust and years of stagnation in browser innovation.

Re: React Makes You Sad?

#160

Post by badthingfactory »

kruhft wrote: post #10

I've just started playing with React and my general opinion is that it's a very 'Facebook' project. Lots of restrictions on what you can do and when keeping all of the coders in line with what you're supposed to be doing and following the 'Facebook' way of programming. I'm sure it's great for writing traditional crud apps, but anything outside of the box that it wasn't intended is a major pain requiring major hacks j…

React is actually a poor choice for traditional CRUD apps in my opinion. React is at its best when you have a large amount of state to manage.
Post reply on HN