News for hackers. Stuff that matters.
Re:React Won by Default – and It's Killing Front End Innovation by sensanaty on Tuesday September 16, 2025 @05:05AM (#45259838)
If after nearly a decade swarms of people are still making the exact same mistakes with how they use a specific method exposed by the library, then the problem isn't with the hundreds/thousands of people making the mistake, the design of the method is broken. This type of issue simply does not exist in Vue or Svelte even if people abuse watchers (which I've anecdotally noticed tends to happen from React devs writing Vue code).

Also I just want to point out again that Dan Abramov had to write an insanely long guide to using useEffect [1]. This piece is around 10k words explaining in-depth how useEffect works. That is insane for one of the fundamental, core methods exposed by a library.

[1] https://overreacted.io/a-complete-guide-to-useeffect/

Re:React Won by Default – and It's Killing Front End Innovation by gloosx on Tuesday September 16, 2025 @08:18AM (#45261236)
You know for thousands of years people are still stepping on rake, the spikey part. And they get hit in their foreheads. The rake is lever by design, but I wouldn't say the problem is the rake.
Re:React Won by Default – and It's Killing Front End Innovation by recursive on Tuesday September 16, 2025 @11:41AM (#45263779)
I've spent more hours using rakes than `useEffect()`, but I've only had the problem with one of them.
Re:React Won by Default – and It's Killing Front End Innovation by wredcoll on Tuesday September 16, 2025 @02:15PM (#45265791)
A) exactly how many people in alk of history have ever actually done that?

B) rakes can't be changed to prevent that, software apis can.