4 ms·
>React becomes useful when you have really complex and dynamic websites, not when you're building basic CRUD todo applications I realize you're just trying to
by rhapsodic 8y ago
>React becomes useful when you have really complex and dynamic websites, not when you're building basic CRUD todo applications
I realize you're just trying to be dismissive, but in point of fact, my CRUD applications are far more complex than basic todo applications.
- diggan 8y agoSorry, was not meant to be dismissive, maybe the "basic" and "todo" was too much. Basically, unless you need dynamic elements on a page, you're better off without JavaScript. If you have lots of them, React might help.
- ben509 8y agoYou can do a fairly complex system by yourself with a simpler scheme because you have a mental model of how things are organized. It's when you throw more developers into the mix that you run into issues.
- rhapsodic 8y ago>You can do a fairly complex system by yourself with a simpler scheme because you have a mental model of how things are organized. It's when you throw more developers into the mix that you run into issues. I think that's a fair point. And I think others have remarked that it illustrates Conway's Law.[1] For a front end like Facebook's, that has numerous moving parts, developed by different teams scattered all over the world, and those parts have to fit together and work together in combinations that may not even be foreseeable, then a framework like React may be the only possible way it could be successful. [1] https://en.wikipedia.org/wiki/Conway%27s_law https://en.wikipedia.org/wiki/Conway%27s_law
- swman 8y agoThen don't use react if you don't need/want to. However, it certainly makes many things easier for development for complex applications especially on greenfield projects.