I started learning React for starting a large project a few months ago. I have not really liked the experience very much. One seems to still need to know all the JS/CSS/HTML I've been using for 10+ years but also a new stack on top of it, simultaneously.
Hooks are one of the strangest features I've seen in a language yet. I doubt they will be a lasting paradigm outside of the React ecosystem.
I like JSX a lot. The idea of reusable stateless components is totally on the right track.
I've found React to be very hard to debug. I get stack traces that don't seem to start from any code I've written.
I now somehow suspect that the next wave in the JS ecosystem will be doing something like microservices on the frontend - message passing between isolated webworkers? I ponder this because React has not, for me, achieved any level of enforcing a sane way of deciding which objects in memory belong to a given component. Something feels really wrong with the the React model of programming.
Writing a project in React seems doubly frustrating - there's the challenge of a new stack and new programming model, but I don't seem to be getting anything for the trade: the code isn't easily debuggable, doesn't have a great upgrade and maintainability story, the app still has race conditions, memory leaks, browser incompatibilities, tightly coupled components. The problem seems to be that React only gently encourages, but does not enforce, any good practices.
Hooks are one of the strangest features I've seen in a language yet. I doubt they will be a lasting paradigm outside of the React ecosystem.
I like JSX a lot. The idea of reusable stateless components is totally on the right track.
I've found React to be very hard to debug. I get stack traces that don't seem to start from any code I've written.
I now somehow suspect that the next wave in the JS ecosystem will be doing something like microservices on the frontend - message passing between isolated webworkers? I ponder this because React has not, for me, achieved any level of enforcing a sane way of deciding which objects in memory belong to a given component. Something feels really wrong with the the React model of programming.
Writing a project in React seems doubly frustrating - there's the challenge of a new stack and new programming model, but I don't seem to be getting anything for the trade: the code isn't easily debuggable, doesn't have a great upgrade and maintainability story, the app still has race conditions, memory leaks, browser incompatibilities, tightly coupled components. The problem seems to be that React only gently encourages, but does not enforce, any good practices.