News for hackers. Stuff that matters.

A comment on Is React impacted by Meta layoff?. Parent comment

Re:Is React impacted by Meta layoff? by guhidalg on Wednesday November 09, 2022 @12:33PM (#33534977)
Can you expand on why? I’m pretty satisfied with React in that it

1. doesn’t try to be a full framework 2. Is easy to explain (without hooks) 3. Has good inner-loop tooling with hot reload 4. Doesn’t have any insane transpiration requirements

What should I try?

[ Parent | on HN ]
Re:Is React impacted by Meta layoff? by esprehn on Wednesday November 09, 2022 @01:48PM (#33536118)
Is that all still true with modern react? By the time you explain the rules of hooks, concurrent mode and its hooks, and RSC I think the only one that's true is (3).
[ Parent | on HN ]
Re:Is React impacted by Meta layoff? by olivermarks on Wednesday November 09, 2022 @02:05PM (#33536360)
@guhidalg there is nothing 'wrong' with React at all, it's mature and debugged. The issue is the platforms it serves are old and something newer is sure to replace it
[ Parent | on HN ]
Re:Is React impacted by Meta layoff? by doliveira on Wednesday November 09, 2022 @02:22PM (#33536553)
"Doesn’t have any insane transpiration requirements"

Configuring webpack is insane in itself

[ Parent | on HN ]
Re:Is React impacted by Meta layoff? by reducesuffering on Wednesday November 09, 2022 @03:05PM (#33537102)
That's easy: 'npm create vite@latest' done
[ Parent | on HN ]