Say what you will but React JS development is utterly exhausting. Every React project is a totally new stack and there is no consensus in the ecosystem.That is how I feel after having worked on 5 big SPA React JS projects over the course of 5 years.

The structure of these projects was all but similar: most used HOC's, some render props, functions-as-a-child, hooks or rather component lifecycles, some used container-components, some Redux, others sprinkled business logic & state all over, and yet others use a mix of server-side rendering and "hydration"...

I dangerouslySetInnerHTML on LazyExoticComponents, and dared not useEffect on the DO_NOT_TOUCH_OR_YOU_WILL_BE_FIRED root property. Hooks embrace functions, but without sacrificing the practical spirit of React, you see.

I didn't make this up. It's verbatim from the code and the docs.
This is not web development, this is at best a tedious fantasy multiplayer game or at worst, a costly joke.

  • 2
    That sounds like poor leadership / discipline....they would probably dork up any framework if they're doing that kind of thing.
  • 2
    If web development was a pair of undies, react would be a shit stain.

    I will ++ anyone who throws shit at react and if you're in london you can also get a pint or nine once this fucking covid bullshit is done with
  • 3
    React rewards that kind of behavior. Why I stick with more opinionated options.
  • 0
    @SortOfTested care to elaborate? curious what you meant with "that kind of behavior" and which opinionated option you use
  • 1
    @N00bPancakes most devs (& humans) care more about the fastest way to get from A to B than whether it is theoretically pure. An application framework/ library should help them achieve that. If so many users, smart or less curious, intuitively do it wrong, something has to be said about the 'solution' itself. And even the most disciplined developer might give in to laziness at times.
  • 0
    You can hardly Vue perspective of SEOs rewarding this bs in code.
Add Comment