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

191–200 of 211 posts

Re: React Makes You Sad?

#191

Post by tiglionabbit »

et1337 wrote: post #172
tiglionabbit wrote: post #137

Earlier quoted context omitted.

He praises React because it makes it easy to change the UI design at any time in response to new requests from the designers. The hard parts he talks about are animations, pre-loading, and virtual rendering, which require some higher level orchestration to get right in any framework. You have to have some component keeping track of this stuff. They mentioned that they had to extend the standard transition component t…

> He praises React because it makes it easy to change the UI design at any time in response to new requests from the designers. Does it though? I suspect their system is fairly brittle after all that "higher level orchestration". I keep seeing this pattern repeat in different software disciplines. Unity is the same way: fantastic for prototyping, but often more painful in the long run. It reminds me of a wise saying…

This conversation could be had about any abstraction. They help with some things and hinder other things.

In this case, a purely functional transformation from application state to HTML means you don't have to think about every possible transition between states like you would in a normal jQuery application. However, since you are not thinking about transitions, implementing transition animations will be harder.

Re: React Makes You Sad?

#192

Post by parasubvert »

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."

There's a new generation of web devs that are starting to feel old and cranky. jQuery will be 10 years old this year (I KNOW!?); Gnarls Barkley's Crazy was on the radio then.

Re: React Makes You Sad?

#194

Post by auggierose »

untog wrote: post #23
auggierose wrote: post #7

Lol. I found React interesting, too, but I don't like to read Javascript code, so I rolled my own React-like framework in Scala. Life is so much easier if you don't have to depend on other peoples mess.

Life is so much easier if you don't have to depend on other peoples mess. Future-you is going to look back on this comment and curse loudly.

I am already future me as I did this about 1.5 years ago :-)

The stuff is not open-source yet, but reading most of the comments here I wonder why anyone would want to open-source things? To meet the friendly people of HN? ;-)

Re: React Makes You Sad?

#196

Post by goldbrick »

danabramov wrote: post #190
goldbrick wrote: post #84

Earlier quoted context omitted.

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.

I was already using es6 classes so I didn't have the choice. I couldn't get 0.14 to work otherwise.

Re: React Makes You Sad?

#197

Post by danabramov »

goldbrick wrote: post #196
danabramov wrote: post #190

Earlier quoted context omitted.

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.

I was already using es6 classes so I didn't have the choice. I couldn't get 0.14 to work otherwise.

Not sure I understand you. You are saying that

1. Transitioning to 0.14 forced you to rewrite something (what? how? I assumed you meant transitioning to ES6 classes which wasn’t necessary but it seems like you meant something else)

2. What choice was it that you didn’t have? Just like 0.13, 0.14 (and 15 soon) allows you to use either ES6 classes or React.createClass(). Both approaches work and will keep working. What are you referring to?

It would really help if you could share at least a simple code example demonstrating your pain points. I want to help! Cheers.

Re: React Makes You Sad?

#198

Post by ENGNR »

mrharrison wrote: post #58

I want to start using React but I think I'm going to stick with Angular for now. I have all of the gotchas of Angular figured out and I think I want to wait another year for the dust to settle on React. By looking at the flowchart it looks like the React ecosystem is still quite Alpha and learning to grow up.

As someone who came from angular, if your app is going to get large react is far better than angular.

For small pages / forms angular is in the sweet spot, so it depends on how your application is setup (not to say you can't do large apps.. but performance is harder in angular)

Re: React Makes You Sad?

#199

Post by kawera »

spankalee wrote: post #180
kawera wrote: post #100

Earlier quoted context omitted.

Why not Web components directly? (genuinely interested, soon I'll have to chose one way or another for a new project)

I work on a web components library, so I'm very biased here, but web components will very soon have broad compatible support across all the major browser engines. It's the only interoperable solution going forward, because every framework out there right now is a silo unto itself.

Thanks, that's my understanding too. I've used Polymer in the past but before 1.0, will look at it again. No doubt web components are the future though, I only wonder if widespread browser support will be a reality in a 12-18 months timeframe.

Re: React Makes You Sad?

#200

Post by vcarl »

SomeCallMeTim wrote: post #185
vcarl wrote: post #118

Earlier quoted context omitted.

>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

Fair enough, low latency, high interactivity applications aren't well suited, but those will always benefit from being as "bare metal" as possible.
Post reply on HN