blog/why-react-isnt-dying #92
Replies: 6 comments 4 replies
-
While it's funny to me seeing "React gave us a predictable way to render our UI" with all the latest Suspense behaviour, fetch patching etc., in this context, I completely agree with that React experimented with "revolutionary" (in UI dev world) concepts that are now been built upon by modern solutions (how fast can calling software a "modern solutions" age with the current eco-system? 🤭). If React would stop investing in R&Ds and iterate on the ways to improve right now, that's where I draw the "it's dead" line. With the current eco-system and tools its been compared to, I don't think it's happening any time soon, though. One big concern about React "dying" I have they keep investing and breaking "the experience" by making changes "inspired" by backwards-compatibility, which you can see in how slow the classes to hooks transition was and the most recent example: the negative talk about CRA experience and how "outdated" of experience it is. I feel like in the software field, being an innovator implies you need to sacrifices some of that 100% compatibility and avoid looking back at your past too much. Otherwise, you start to loose your momentum and that's where devs start to "loose interest" and consider you "dead". |
Beta Was this translation helpful? Give feedback.
-
Hm, see your article on daily.dev. I notice that more and more entries from daily.dev are pure advertisments. |
Beta Was this translation helpful? Give feedback.
-
I agree with many of the points listed, but one point that I don't agree with so much is related to the ecosystem, because despite having much less specific libraries for the framework there is also a smaller need for specific libraries |
Beta Was this translation helpful? Give feedback.
-
React is the best out there. The problem is with elite anti patterning that is trying to gatekeep themeselves into relevance, but actually harming to coding community. Custom hooks are a great general disparity in programming and while they have some benefits, they do not have all the benefits and could considerably be dropped and foregone. Functional components is the general best possible pattern ever invented and everything can be done inside of them using cohesion. The sooner the community understands this, the better we will all be by just relaxing and doing what already works and is 100% verified and tested. |
Beta Was this translation helpful? Give feedback.
-
Having more libraries available does not mean better support. Take a look at the Angular and Svelte communities, they have almost everything they need baked in and don't need much other than UI enhancements and CSS frameworks. React is dead to me considering that it decided for the hooks and functional component anti-pattern. UI will always be best represented by objects because state has to be saved to memory anyways. The more I repeat this, the easier it will become over time for people to start catching on and dropping React. |
Beta Was this translation helpful? Give feedback.
-
Great post. Your "growth loop" explanation was really interesting. Thanks |
Beta Was this translation helpful? Give feedback.
-
blog/why-react-isnt-dying
Finishing my train of thought about why React is here to stay (for now).
https://tkdodo.eu/blog/why-react-isnt-dying#inject-comments
Beta Was this translation helpful? Give feedback.
All reactions