3 ms·

Just people who don't understand how to write performant React, honestly. There are ways of writing React that result in vast numbers of re-renders... it's not

Just people who don't understand how to write performant React, honestly. There are ways of writing React that result in vast numbers of re-renders... it's not a best practice, but it's relatively easy to make happen, especially if you ignore the official recommendations and pull Stackoverflow answers from 2015.

internetter 4y ago
Sure, to some degree, but you have to wonder why it's so easy for developers to footgun themselves. It's the fault of the language, imo, not bad developers.
- Yoric 4y ago
  What would prevent that?
  - internetter 4y ago
    I believe the term is "fine grained reactivity". Basically, components do not rerender when data updates, only the specific part of the DOM dependent on that data. This alleviates all the footguns that come with rerenders (including the infamous infinite loop) and often results in cleaner code. I'm partial to solid[0] (there are lots of comparison articles, but I think [1] and [2] show it the best). I believe svelte is similar and vue is experimenting with this as well [0]: https://www.solidjs.com/ https://www.solidjs.com/ [1]: https://news.ycombinator.com/item?id=30508524 https://news.ycombinator.com/item?id=30508524 [2]: https://news.ycombinator.com/item?id=35061672 https://news.ycombinator.com/item?id=35061672
    - deleted 4y ago
      [deleted]
    - jakelazaroff 4y ago
      That isn’t always true. Reactivity can make updates faster, but adds more overhead to creating DOM nodes because you need to set up the subscriptions that are used to eventually update them. To steal a phrase originally about VDOM: “reactivity is pure overhead”. Nothing comes for free!
      - internetter 4y ago
        Maybe in theory, but solid still outperforms react in creations by a considerable amount, and I think most applications will find they are doing a lot more rerenders than insertions anyway
- justrealist 4y ago
  I've never seen a language or framework that is both easy to be quickly productive in, and free of footguns. React is easy to be quickly productive in... thus, it has footguns.
- Marazan 4y ago
  React is easy to use without understanding the component lifecycle. The penalty is poor performamce rather than a non-functional app. You saw the same thing in the before times with Adobe Flex. So much code from people who had no understanding of the lifecycle - apps that worked but were appallingly slow and buggy.

internetter 4y ago

Sure, to some degree, but you have to wonder why it's so easy for developers to footgun themselves. It's the fault of the language, imo, not bad developers.

Yoric 4y ago
What would prevent that?
- internetter 4y ago
  I believe the term is "fine grained reactivity". Basically, components do not rerender when data updates, only the specific part of the DOM dependent on that data. This alleviates all the footguns that come with rerenders (including the infamous infinite loop) and often results in cleaner code. I'm partial to solid[0] (there are lots of comparison articles, but I think [1] and [2] show it the best). I believe svelte is similar and vue is experimenting with this as well [0]: https://www.solidjs.com/ https://www.solidjs.com/ [1]: https://news.ycombinator.com/item?id=30508524 https://news.ycombinator.com/item?id=30508524 [2]: https://news.ycombinator.com/item?id=35061672 https://news.ycombinator.com/item?id=35061672
  - deleted 4y ago
    [deleted]
  - jakelazaroff 4y ago
    That isn’t always true. Reactivity can make updates faster, but adds more overhead to creating DOM nodes because you need to set up the subscriptions that are used to eventually update them. To steal a phrase originally about VDOM: “reactivity is pure overhead”. Nothing comes for free!
    - internetter 4y ago
      Maybe in theory, but solid still outperforms react in creations by a considerable amount, and I think most applications will find they are doing a lot more rerenders than insertions anyway
justrealist 4y ago
I've never seen a language or framework that is both easy to be quickly productive in, and free of footguns. React is easy to be quickly productive in... thus, it has footguns.
Marazan 4y ago
React is easy to use without understanding the component lifecycle. The penalty is poor performamce rather than a non-functional app. You saw the same thing in the before times with Adobe Flex. So much code from people who had no understanding of the lifecycle - apps that worked but were appallingly slow and buggy.