> Adding a view library is helpful, but with it these days comes state management, routing, graphql, SSR, hot reloading, CSS-in-JS, and just mountains and moun

> Adding a view library is helpful, but with it these days comes state management, routing, graphql, SSR, hot reloading, CSS-in-JS, and just mountains and mountains of related things just to get your app running. It feels like the author is confused between react (the library) and the its ecosystem. They don't need all those things in order to use React. - Routing: Not mandatory. You can just use server side routing. You're no longer a SPA in this case, but do you need to be a SPA ? - SSR: I actually do not understand the new obsession with SSR. If you need SEO, add a static marketing page, that might be enough for a lot of scenarios. - CSS-in-JS: just write a plain css file and class names - State management: useState + context API works for a lot of simple apps. I don't even understand why "hot reloading" is even listed in the complaints. It's a nicety, not a requirement. It's not even "react".