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

React 19 Breaks Async Composability

github.com

Post reply on HN
Print view View original

11–20 of 114 posts

Re: React 19 Breaks Async Composability

#11

Post by JakaJancar »

wtf242 wrote: post #4
nikanj wrote: post #2

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

I've adopted the practice of avoiding libraries with major version > ~3. If you needed to re-design your API so many times, I don't trust your judgement enough to build on top of it.

That said, I still use React and... it's at 19.x :'(

Re: React 19 Breaks Async Composability

#12

Post by akritrime »

teitoklien wrote: post #8
ibash wrote: post #3

Earlier quoted context omitted.

Class components was the last good react idea.

Functional Components are 10x easier and cleaner to use in React

You could already use functional components before. The main issue with React now is all these hooks and effects.

Re: React 19 Breaks Async Composability

#13

Post by thibaut_barrere »

interstice wrote: post #6
wtf242 wrote: post #4

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

To be fair I’ve had similar issues with Rails

In that regard, my experience has been the following churn scale:

JavaScript churns more than Rails which churns more than Elixir/Phoenix.

I believe this is caused by “how sound the fundamentals are” (technical debt in the language itself and its stdlib).

Re: React 19 Breaks Async Composability

#15

Post by FriedrichN »

wtf242 wrote: post #4
nikanj wrote: post #2

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

Just the fact that Yarn seems to be the dominant package manager now when it seems like last week it was npm. What will it be next week?

I truly wonder, do people use this stuff for software that is expected to be maintained for 5-10 years? I feel that with the speed at which everything changes, gets deprecated, discontinued, succeeded, etc. you'll spend a good chunk of your time staying up to date with the current js ecosystem. That doesn't seem very economic to me.

Re: React 19 Breaks Async Composability

#17

Post by azangru »

wtf242 wrote: post #4
nikanj wrote: post #2

I 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 to React itself, it evolves quite slowly and cautiously. It is almost the same now as it was in 2019. But the closer your stack is to the native browser apis, the more robust and long-living it will be, which is why I have faith in Lit.

Re: React 19 Breaks Async Composability

#18

Post by colordrops »

FriedrichN wrote: post #15
wtf242 wrote: post #4

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

Just the fact that Yarn seems to be the dominant package manager now when it seems like last week it was npm. What will it be next week? I truly wonder, do people use this stuff for software that is expected to be maintained for 5-10 years? I feel that with the speed at which everything changes, gets deprecated, discontinued, succeeded, etc. you'll spend a good chunk of your time staying up to date with the current j…

Naw it's back to npm

Re: React 19 Breaks Async Composability

#19

Post by crooked-v »

akritrime wrote: post #12
teitoklien wrote: post #8

Earlier quoted context omitted.

Functional Components are 10x easier and cleaner to use in React

You could already use functional components before. The main issue with React now is all these hooks and effects.

The whole point of hooks is to substantially simplify "effects stuff", as compared to the total uncomposability of class components.

While the specific implementation of hooks has its bugbears, I think it's pretty telling that nobody else is using class components either, even in projects with fundamentally different engines like Svelte.

Re: React 19 Breaks Async Composability

#20

Post by anonzzzies »

wtf242 wrote: post #4
nikanj wrote: post #2

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

I had the same issues with rails, although that’s a while ago; not sure if it improved.
Post reply on HN