Feels a lot like a lengthier, polemical way of saying that frameworks become popular because they allow more people to do more stuff more easily. But this is bad because businesses benefit or something. None of the ideas here stand up to scrutiny. For example, Angular with its more opinionated design and framework approach was a much better choice for regularizing developer effort and making devs fungible. But by all…
> become popular because they allow more people to do more stuff more easily Nope. Because they allow people to be easily replaced. Nothing to do with how easy or good the framework is. That's the whole point of the article.
Having frameworks that allow more devs to do more things means correspondingly that more people can be hired for those things with less training. In this respect, there is an obvious overlap between employer and developer interests.
Take MongoDB from the article. IME the biggest advocates for MongoDB are not managers (who barely have any idea what it is). It's developers who just want an "easy" way to store data that corresponds closely to the JSON document format they are used to, and doesn't force them to think about "annoying" and "outdated" things like relational modeling, joins and schema migrations.
If fungibility and lowest common denominator hiring drove the popularity of dev tools, then .NET and Angular would be ruling the roost.