If you are are starting from scratch, isn't the answer to which language to use just "the framework that best supports the business case and problem you are working on"?

If that produces many options, then choose based on the team's familiarity with the language, frameworks, and ecosystems.

A good software engineer should be pretty language agnostic when it comes to work, even if they have a personal aesthetic or technical preference.

The point of the article is that if you attempt to find

> "the framework that best supports the business case and problem you are working on"

by asking the people who will be using it, then the answer will almost certainly be wrong.

The whole point here is working out which is the best tool is almost impossible because of natural human cognitive biases.

TL;DR summary:

No. No, that isn't the answer. It's not even an answer. It's the answer to a different question.