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

181–190 of 211 posts

Re: React Makes You Sad?

#181

Post by dang »

joslin01 wrote: post #85

I don't know what's worse. A poorly-worded expression of someone's experience with React, or the no-info-or-even-attempt-to-understand judgment from you. Oh man, you're a guy who does a fair amount of React work and tries to pay attention to weird arguments against it? Let me immediately downvote that guy and upvote you! What's so weird about someone not enjoying the rigidity React offers and realizing that Facebook…

No personal attacks on HN, please.

We detached this subthread from https://news.ycombinator.com/item?id=11196675 and marked it off-topic.

Re: React Makes You Sad?

#182

Post by danabramov »

shruubi wrote: post #170

Am I the only one that finds it weird that this entire chart is about morphing how you use React into something that works for you rather than helping you evaluate your needs and identify what might be a non-react solution. Why are we as an industry suddenly so married to the idea that rather than evaluating other solutions we should just hammer away at React until it works for what we need?

Because this is exactly what people do before writing sad posts about how you “have to” use Flux, ES6, Webpack to use React. People get that impression because they search for “React boilerplates” and extrapolate. It’s great that you avoided this trap!

Re: React Makes You Sad?

#183

Post by danabramov »

octref wrote: post #148
danabramov wrote: post #113

Earlier quoted context omitted.

Check out https://github.com/ryanflorence/react-project , it’s very new but seems similar to what you are aiming for.

Isn't that exactly what he's not aiming for, namely "15 files and 900 lines of configuration that seem completely overkill"? This seems to remove complexity but it just hides the complexity in the dependency. When something doesn't work out or he wants to change the behavior he still has to delve into these "15 files and 900 lines of configuration".

It has focus on great production features without diving into config until you are ready.

For something more approachable but less powerful check out https://github.com/insin/nwb.

Re: React Makes You Sad?

#184

Post by danabramov »

c0ffe wrote: post #158

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.

Not sure what your point is about th shotgun. The point of that export is to keep supporting old API with a deprecation warning while it is being moved into another package. It is temporary.

Re: React Makes You Sad?

#185

Post by SomeCallMeTim »

vcarl wrote: post #118
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…

>Does it seem that the entire industry has migrated to this stack, whether or not it really makes sense for everyone to? It definitely doesn't make sense for all types of websites, but React seems to me like a solid choice any time a) a true web application is desired and b) maintainability, interactivity, and scalability are high priorities. React isn't the best choice for static informational sites and such, but I…

> but I can't think of an application that wouldn't be well suited to React.

A truly complex app where speed is crucial. [0] Like Atom. [1]

[0] https://aerotwist.com/blog/react-plus-performance-equals-wha...

[1] https://github.com/atom/atom/pull/5624

Re: React Makes You Sad?

#186

Post by SomeCallMeTim »

vcarl wrote: post #118
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…

>Does it seem that the entire industry has migrated to this stack, whether or not it really makes sense for everyone to? It definitely doesn't make sense for all types of websites, but React seems to me like a solid choice any time a) a true web application is desired and b) maintainability, interactivity, and scalability are high priorities. React isn't the best choice for static informational sites and such, but I…

> but I can't think of an application that wouldn't be well suited to React.

A truly complex app where speed is crucial. [0] Like Atom. [1]

[0] https://aerotwist.com/blog/react-plus-performance-equals-wha...

[1] https://github.com/atom/atom/pull/5624

Re: React Makes You Sad?

#187

Post by danabramov »

grumblestumble wrote: post #101
danabramov wrote: post #63

Earlier quoted context omitted.

Thank you for the criticism! Would you like to help me understand its flaws better so I can improve in the future?

3 things: 1. Much of it reads as"are you taking this approach? yes? don't take this approach. no? take this approach." 2. There are also a couple of flowchart errors ("are you working on a production app" appears twice for no reason). 3. The main reason React makes me sad is the need for excruciating flowcharts like this. As a result, the entire thing comes across as self-parody. For context, I'm a developer who work…

If you take a close look at both flows you will see that point 1 and point 2 actually explain each other. :-)

If you use React in production and don’t use a bundler, you should. If you don’t use React in production and do use a bundler, perhaps you shouldn’t because it will distract you from learning process. Does that help?

The “need” for flowcharts like this comes from lots of misleading information on the internet about React, not from React itself.

Thank you for your comments!

Re: React Makes You Sad?

#189

Post by sergiotapia »

beefsack wrote: post #169
sergiotapia wrote: post #165

Give React a try with Meteor and your head will explode. Suddenly everything works out of the box, you get nice ES6 syntax out of the box, files structure is flexible out of the box - notice a trend? Meteor and React is hands down the best way to use React in my honest opinion. Meteor 1.3 will come out very soon and will have full NPM and module support, after that I think Meteor will take the web by storm and become…

Does Meteor scale to hundreds of concurrent users yet? I've used it multiple times in the past and have always hit performance barriers even at tens of users, and have found it make scaling your infrastructure nigh on impossible.

Yes it does, easily. And scaling is even easier when you use React because you 'subscribe' to data when the component is 'mounted' and when the component is destroyed you remove that subscription.

And this all happens for you automatically. No lie, React makes Meteor scale by virtue of how it forces you to architect your data usage.

Re: React Makes You Sad?

#190

Post by danabramov »

goldbrick wrote: post #84
danabramov wrote: post #68

Earlier quoted context omitted.

Can you please help me understand the issue by providing a specific example of how a new React release introduced churn in your project?

Sure, I started a react project and got everything working with es6 and babel in October. In December I upgraded to react 0.14 and had to refactor all the things. It was extremely difficult to figure out how to solve some of the arbitrary-seeming changes, such as now having to re-bind all of the methods in the constructor.

Wait, why did you refactor all things? I’m afraid you have been misinformed. :-(

Please read the official release notes when upgrading.

Nowhere does 0.14 say you need to change components to use classes. They are allowed now (since 0.13) but React.createClass() is still there and is not going away any time soon. I’m afraid you listened to bad advice.

Post reply on HN