You're just making the author's point for them. A more opinionated framework that matched the team that was supposed to code with it would have worked better for them over the lifecycle of the project.
Most enterprise teams are poorly skilled with bad leadership. Modern frameworks and coding paradigms are a bad fit.
> A more opinionated framework that matched the team that was supposed to code with it would have worked better for them over the lifecycle of the project.
No it wouldn't, not for an enterprise application that is supposed to last a decade or more. Instead you want to use standards such as Web Components that will last essentially forever.
Now that's just silly. Longevity of the enterprise application is of no concern at all. The only things that matter is on-time and on-budget. If you can't deliver that, then you run into the problem the author of the article ran into, his bosses yelling at him and his career and job in jeopardy.
If the project develops issues after all the initial stakeholders have moved on, it's the new stakeholders' problem.
Most enterprise teams are poorly skilled with bad leadership. Modern frameworks and coding paradigms are a bad fit.