Amen. If you could spin a turbine with the ire directed towards frontend engineering on this forum alone, we could retire the sun. I think there's a defensive

Amen. If you could spin a turbine with the ire directed towards frontend engineering on this forum alone, we could retire the sun. I think there's a defensive quality to it. It was at one point an overwhelming meme that writing JS was somehow not "real programming", that writing web apps is "easier", and lots of engineers who should otherwise know better internalized that and then apparently froze in time. Then when they try to hack it for themselves and encounter any resistance at all, they get edgy and form ignorant opinions that boil down to "I hate React because I got frustrated and React was there". Turns out the skill transfer does work in reverse though. On the backend your code often only has to run in one environment, with machine specs you get to choose, and responses for most things are fine measured in seconds. Unbelievable luxury. React is, for its utility, an incredibly minimal library. It's hard to point to anything in it that it really shouldn't be responsible for. Most of the problems it solves with that minimal layer are among the very first problems you run into trying to build any serious web application no matter the stack or structure. Even if you don't use React, you'll either write bespoke spaghetti UI update code or more likely you'll end up with the pieces of something that sure as hell looks like React if you squint.