You're not stupid for using a framework, and nobody has pulled a fast one on you. https://seldo.com/posts/the_case_for_frameworks
The case for frameworks

Today I read Alex Russell's post The Market for Lemons and I found myself compelled to write a rebuttal. I am a big fan of Alex's work in general but not of this post in particular, which is very long, so allow me to attempt to summarize it

@seldo economics indeed but the changing storyline is also well documented (yes that's grifting!)

And also ppl need to know how HTML/etc work in order to use React not the other way around.

@brianleroux I do not think everybody is using React because Guillermo is just really, really persuasive.
@seldo @brianleroux You're stating this like it's facially ridiculous, but I don't see why it is. "Persuasive" not just meaning personally persuasive, but persuasive with the backing and credibility of Facebook? This does not seem particularly far-fetched.
@agocke @brianleroux Millions and million of developers are using React. In surveys I run they report high satisfaction with React. They're not just using it because they were impressed with it, or because somebody told them to. Developers really like React, and I have thousands of data points to prove it.
@seldo @brianleroux Fair enough, but I think it's a point you have to argue with data! Not immediately obvious.

@agocke @seldo I didn't see the part where anyone was debating devs like it or use it.

The points made by Alex and others are concerned with the poor outputs and the advocates changing their stories. (See your colleagues Zach's post about React criticism for ex.)

@brianleroux @agocke The flaw in Alex's argument is that he focuses only on the (admittedly bad!) results React gets for low-power mobile devices. My point is that developers are not *unaware* of the bad outcomes, they like React *despite* the bad outcomes, so let's look at why. The idea that developers  cannot see that bad outcomes, poor creatures, only Alex can, is why the whole thing comes off as insulting.
@brianleroux @agocke We, the developers of the world, are aware that we are making a trade-off and we are making it anyway, so continuing to yell at us that the trade-offs we knowingly made were bad is not going to do anything but get us annoyed. We KNOW.
@seldo @agocke so are we supposed to pretend it's good and bad web experiences are good for consumers?
@brianleroux @seldo @agocke I think @seldo is saying that shaming developers or treating like they donโ€™t know what they are doing doesnโ€™t make things any better for consumers either.
@ThePaulMcBride @brianleroux @agocke Exactly. Our energy would be better spent meeting them where they are -- using frameworks by the millions, making rich apps -- and reduce the harm by making the frameworks better. Write something they like *better* than React rather than just telling them it's bad.
@seldo @brianleroux @agocke fixing the perceived problems with React would be huge too. A lot of things will never be rewritten because itโ€™ll be better for users. However upgrading to a new version of React or Next etc is usually much less work.
@ThePaulMcBride @seldo @agocke not having to upgrade because your shit is based on web standards is clearly better than spinning tyres on same functionality isn't it?