4 ms·

Genuine question... but is the DevEx of modern React actually better than what it was back in ye-olden-days? I don't use React (I main Vue), so I can't speak a

Genuine question... but is the DevEx of modern React actually better than what it was back in ye-olden-days? I don't use React (I main Vue), so I can't speak authoritatively. But as an outside observer it feels like React gets progressively more and more "mind-bendy" with every passing year, and when I look at some high-complexity React apps my mind nearly explodes with the amount of crazy complexity that needs be managed to keep the things behaving the way they're meant to.

Zetaphor 2y ago
Echoing this, the approach Vue takes is SO much simpler and yet it still manages to accomplish the same end results. With each new release React becomes increasingly reliant on wonky React-specific abstractions that feel more like a sunk-cost fallacy than actually meaningful solutions to building a reactive SPA. I personally believe a lot of React developers are experiencing the framework equivalent of Stockholm Syndrome. I would encourage any React devs reading this to go look at the Vue composition API and then try to explain why all of these increasingly convoluted abstractions are necessary.
- SebastianKra 2y ago
  Could you go into detail? To me it seems like the same concepts exist in Vue: useState -> ref useEffect -> watchers useRef -> template-refs The only difference I see, is that Vue rerenders nothing by default whereas React rerenders everything by default. And I admittedly agree with Vue on this one, but it's not enough to make me give up the superior ecosystem and JSX. The boilerplate for creating computed's is comparable to setting up useMemo calls. And oh look: the justification for computed is exactly the same as useMemo/useCallback: https://vuejs.org/guide/essentials/computed.html#computed-caching-vs-methods https://vuejs.org/guide/essentials/computed.html#computed-ca...

4 ms·

Genuine question... but is the DevEx of modern React actually better than what it was back in ye-olden-days? I don't use React (I main Vue), so I can't speak a

by llamaLord 2y ago

Zetaphor 2y ago
Echoing this, the approach Vue takes is SO much simpler and yet it still manages to accomplish the same end results. With each new release React becomes increasingly reliant on wonky React-specific abstractions that feel more like a sunk-cost fallacy than actually meaningful solutions to building a reactive SPA. I personally believe a lot of React developers are experiencing the framework equivalent of Stockholm Syndrome. I would encourage any React devs reading this to go look at the Vue composition API and then try to explain why all of these increasingly convoluted abstractions are necessary.
- SebastianKra 2y ago
  Could you go into detail? To me it seems like the same concepts exist in Vue: useState -> ref useEffect -> watchers useRef -> template-refs The only difference I see, is that Vue rerenders nothing by default whereas React rerenders everything by default. And I admittedly agree with Vue on this one, but it's not enough to make me give up the superior ecosystem and JSX. The boilerplate for creating computed's is comparable to setting up useMemo calls. And oh look: the justification for computed is exactly the same as useMemo/useCallback: https://vuejs.org/guide/essentials/computed.html#computed-caching-vs-methods https://vuejs.org/guide/essentials/computed.html#computed-ca...