React 19 Breaks Async Composability
github.com
React 19 Breaks Async Composability
1–10 of 114 posts
Re: React 19 Breaks Async Composability
#2I find it fascinating how frequently the best practices change, and how dogmatically people still want to follow best practices. As an industry, we spend absolutely incredible amounts of work refactoring working code into the new paradigm.
Re: React 19 Breaks Async Composability
#3I find it fascinating how frequently the best practices change, and how dogmatically people still want to follow best practices. As an industry, we spend absolutely incredible amounts of work refactoring working code into the new paradigm.
Class components was the last good react idea.
Re: React 19 Breaks Async Composability
#4I find it fascinating how frequently the best practices change, and how dogmatically people still want to follow best practices. As an industry, we spend absolutely incredible amounts of work refactoring working code into the new paradigm.
It's insane how toxic the js environment is. it seems like if a project is over 6 months old, nothing will work. When I yarn install on an old project, i'm rolling the dice. I had a 2 year old next.js side project i was working on and the amount of work to make it work the latest version with just updating the dependencies and reading the upgrade docs were infinitely more complex than just starting over from scratch.
no thanks. I will stick with Rails.
Re: React 19 Breaks Async Composability
#5What does that mean? (for someone not familiar with React)
Re: React 19 Breaks Async Composability
#6I find it fascinating how frequently the best practices change, and how dogmatically people still want to follow best practices. As an industry, we spend absolutely incredible amounts of work refactoring working code into the new paradigm.
It's insane how toxic the js environment is. it seems like if a project is over 6 months old, nothing will work. When I yarn install on an old project, i'm rolling the dice. I had a 2 year old next.js side project i was working on and the amount of work to make it work the latest version with just updating the dependencies and reading the upgrade docs were infinitely more complex than just starting over from scratch.…
To be fair I’ve had similar issues with Rails
Re: React 19 Breaks Async Composability
#7I find it fascinating how frequently the best practices change, and how dogmatically people still want to follow best practices. As an industry, we spend absolutely incredible amounts of work refactoring working code into the new paradigm.
It's insane how toxic the js environment is. it seems like if a project is over 6 months old, nothing will work. When I yarn install on an old project, i'm rolling the dice. I had a 2 year old next.js side project i was working on and the amount of work to make it work the latest version with just updating the dependencies and reading the upgrade docs were infinitely more complex than just starting over from scratch.…
The funny thing is that they eventually circled back to server-side rendering. It just has a cool TLA now.
Re: React 19 Breaks Async Composability
#8I find it fascinating how frequently the best practices change, and how dogmatically people still want to follow best practices. As an industry, we spend absolutely incredible amounts of work refactoring working code into the new paradigm.
Class components was the last good react idea.
Functional Components are 10x easier and cleaner to use in React
Re: React 19 Breaks Async Composability
#9I find it fascinating how frequently the best practices change, and how dogmatically people still want to follow best practices. As an industry, we spend absolutely incredible amounts of work refactoring working code into the new paradigm.
I have a harsher take, 95% where react is used it is used without the need.
Re: React 19 Breaks Async Composability
#10Earlier quoted context omitted.
It's insane how toxic the js environment is. it seems like if a project is over 6 months old, nothing will work. When I yarn install on an old project, i'm rolling the dice. I had a 2 year old next.js side project i was working on and the amount of work to make it work the latest version with just updating the dependencies and reading the upgrade docs were infinitely more complex than just starting over from scratch.…
The funny thing is that they eventually circled back to server-side rendering. It just has a cool TLA now.
React's server components is pretty fundamentally different from how something like Rails or old-school PHP does "server-side rendering".
It's a lot closer in spirit to something like Phoenix LiveWire.