4 ms·

jQuery from 2009 also still works today. What I meant was, developers want to use the latest and greatest. Hooks added in 2018 havent changed, there’s no replac

• Raed667 3y ago
  that's one thing I admired about the React team back then, they took the time to think about how things "should" work long term. The functional/hooks release was criticised as people liked their class components, but time has shown that hooks were the correct decision. I feel they lost that as people gradually rotated out of the team, around the time they announced concurrent-mode, now suspense and the half baked RSC "release".
  • nicoburns 3y ago
    Yeah, I'm pretty skeptical about concurrent mode. People have been trying to implement something like this since ~2010, and I haven't seen it done well yet.
• Rapzid 3y ago
  > Component re-rendered because hook 16 updated. DX Amaze.
• troupo 3y ago
  > They got the DX right from the start, that other libraries are still trying to emulate. The DX isn't "right". It's just the one they are sticking to. There are many issues with the actual developer experience when it comes to hooks in React. So it's a good thing that other frameworks are iterating and finding new and possibly improved ways of doing things. E.g. neither Svelte nor Solid require dependency arrays to effects or other reactive primitives. Their effects work everywhere, and not just inside component code. You're not beholden to the order and number of effects, unlike with hooks. Etc.