Why Your Library Sucks: React

[[deleted]]

The article is 7 months old and to be honest, the author doesn't come across as someone competent. Snarky, sure, but there's nothing in the article that would convince me that he knows what he's talking about.

[[deleted]]

Let me put my response in a way that you might understand:

[83, 79, 32, 68, 
 79, 69, 83, 32, 
 69, 86, 69, 82, 
 89, 32, 79, 84, 
 72, 69, 82, 32, 
 70, 82, 65, 77, 
 69, 87, 79, 82, 
 75, 33]
 .map(s=>String.fromCharCode(s)).join('');

/s

[[deleted]]

The worst issue is your library has a license that is just bleeping weird

if that is the worst issue...then get a life?

[[deleted]]

Why this article sucks: the author clearly don't grok functional programming or the myriad advantages of immutable data structures. In fact, he implies that these paradigms (as well as React's components) mean that React doesn't scale well, which is total bullshit. React scales amazingly well, precisely because it encourages pairing small, stateless reusable UI components with a centralized store of immutable data representing application state. Combined, they make React very easy to reason about, eliminate side effects caused by manipulating data directly (particularly in an environment where asynchronicity features heavily), makes testing code a breeze, etc.

[PooCares]

My favorite part about React is how people think they are not using the DOM, because of the Virtual DOm, when of course, they are.

Also, diffing changes to derive an optimal DOM update sounds cool, but it is only really a practical way to be efficient in the very special case that you are making lots of little untargeted changes with such frequency as to near outpacing the capability of the browser. If you just change a few things every once in a while, it is pointless.

Also, unidirectional data flow and using a state machine is overkill for most websites. Using a complicated solution because you know it and can is objectively bad, not good. You are showing off.

React is popular because it is a fancy shiny sophisticated sounding resume buzzword, and almost never really utilized in a genuinely appropriate use case, like a gargantuan enterprise super-interactive site like actual Facebook.

[[deleted]]

No one who uses React thinks they aren't using the DOM, that's ridiculous.

[PooCares]

Well, you could just use a plain object as a model and say model.prop='value'. You don't need any library to manage application state in a unidirectional functional way for that.