IMO choice of language is a design decision. Weighing the pros and cons of a particular language without specifying the use case and project requirements seems ass backwards to me.

To illustrate, consider if we rewrite the title: “Goodbye, Phillips head screwdrivers, I wish you success, but I’m back to flat heads”. Seems silly, doesn’t it?

To be fair though, I imagine this article is written as a reaction to Rust proponents making similar arguments.

> Weighing the pros and cons of a particular language without specifying the use case and project requirements seems ass backwards to me.

Practically every company I talked with about Rust positions named very good reasons to move to it.

N=1 and all, yup, but your opinion is N=1 as well.

There are several very engineering-sound reasons to choose Rust and people are aware of them and are appealing to them when considering it.

Most regular hard-and-fast organizations outside of the SV bubble don't subscribe to this. They will rather tweak design around to match whatever labor pool is available (e.g. Java for most code farms in the past decades).

[dead]