I am with you. I often want to enjoy the magic of something like React, but when your entire coding task is a man day or two it becomes really hard to justify l

I am with you. I often want to enjoy the magic of something like React, but when your entire coding task is a man day or two it becomes really hard to justify learning React. That is my main gripe, many would just say that means "React is not for you" and technically that is obviously true. But in reality it is just the immature tooling around everything getting in the way. It is all in such a state of flux and experimentation that you can't always do things that should be simple simply. I think developers often do their own work disservice by not being a little more careful with dependencies, basically. Someone spends a few days wrangling a pile of NPM packages, build frameworks, and minifiers into this magical state that lets them operate very productively, but it isn't scaleable productivity in that now you have forced the whole developer community to do this multi day learning battle. And now as your whole pile of JS evolves under you, you are committed to this stack and keeping up with the evolution of all the dependencies. You end up with a lot of "least bad" solutions that aren't actually very good to the core problem. I see that as React's biggest problem with adoption. The core model is actually really great, but the usability is a steep learning curve.