5 ms·
Nobody's telling you to use React when you have a static HTML page. But if you ever worked on an app of even medium complexity, you would understand what React
by phailhaus 4y ago
Nobody's telling you to use React when you have a static HTML page. But if you ever worked on an app of even medium complexity, you would understand what React is solving for developers. State management is the problem, and your vanilla JS forms are not going to cut it.
- wruza 4y agoThe problem is, I worked on these, half of my life. And while I agree that declarative rendering has its upsides, I am not blind to downsides and bait-and-switch-complexity tricks. React is pretending to be a functional “not your concern how it’s done” language without any safety nets or execution models these usually provide.
- phailhaus 4y agoIf we agree that declarative rendering has its upsides, then it is ridiculous to keep moaning that the complexity is "nuts" and that everyone's just insane for no reason. React is what a declarative model looks like. It eliminates an entire class of UI, state, and behavior management issues, in exchange for working within its rendering engine. If you're looking to build a complex frontend, that is extremely attractive.
- porker 4y ago> If we agree that declarative rendering has its upsides, then it is ridiculous to keep moaning that the complexity is "nuts" and that everyone's just insane for no reason. React is what a declarative model looks like. Are you saying that Vue isn't a declarative model?
- strokirk 4y agoI’ve actually replaced a bunch of static HTML pages with React, to benefit from TypeScript. I’m horrible with spelling and it helps me a lot.