Hacker News Reader

Comment by pjc50 | Hacker News Reader

I've often felt this is the other way round: Facebook hired a massive frontend team, and therefore they have to continually create work for themselves.

View on HN

The point where they re-centered React around a bad half-implementation of Objects, in a language that already has an OO system, was when I decided they were out of real problems to solve (or didn't know how to approach those real problems—do Forms still suck in vanilla React, without an add-on library or two?) and on to pure employment-justifying and CV-building.

And, more power to them, but at that point I'm not going to willingly rely on the project for anything.

> do Forms still suck in vanilla React, without an add-on library

Did they ever? Wouldn't we just do <form onSubmit={handleSubmit}> and then in the handler we just grab the FormData, send it to the server, get back the response, then update whatever? Doesn't seem like it should be that hard?

Nah, they had real problems that React solved. But most applications aren't Facebook and don't have the same need for this.

React v1 solved a real problem, but perhaps didn't really need 17 subsequent major revisions with another on its way? But that's the different cultures around this discussion. The Javascript community generally seems to subscribe to progress at all cost, which the earlier commenter attributes to exceptionally large teams like that at Facebook trying to find work to do, whereas the Go community generally subscribes to the idea that it is okay to be "done", clamping down on the extent of any future iterations.

To be fair the first major release was 15.0. So there has been there major revisions since then, not 17.

Reply on news.ycombinator.com