The author did not convince me that they had above average due diligence. It's common to go through the motions of required processes/procedures like:

"create decision criteria, do research, validate findings by creating a proof of concept, present findings, document everything in the decision log"

and not generate much value from the process as a result.

Right, but this still isn't the fault of React. My gripe with this article, and view points like this, is that instead of taking ownership it's again the tool that gets blame and just further perpetuates the "js bad" meme.

> And I'm not entirely convinced that it is a good tradeoff in the crazy JS ecosystem where everything is changing and breaking all the time, especially if you are building more complex things.

Right, and if that's your opinion (and a perfectly valid one!) then don't pick the JS ecosystem and cry when it bites you.