Did you read the following paragraph and the section on Abandonment? Erlang isn't mentioned by named, but the problem domain is.

"I expect more of the world to adopt this philosophy as the shift to more distributed computing happens. In a cluster of microservices, for example, the failure of a single container is often handled seamlessly by the enclosing cluster management software (Kubernetes, Amazon EC2 Container Service, Docker Swarm, etc). As a result, what I describe in this post is possibly helpful for writing more reliable Java, Node.js/JavaScript, Python, and even Ruby services. The unfortunate news is you’re likely going to be fighting your languages to get there. A lot of code in your process is going to work real damn hard to keep limping along when something goes awry."

Yup read that part and that's exactly my point.

The author hammers home how important abandonment is in a light threaded system without any mention of all the work that Erlang has been doing for years in that space. Given how much reference there is to Rust, Go and a host of other languages I would at least expect Erlang to be mentioned.

The frequency of the mentions of Go made me prick up my ears so I've done a frequency analysis of language mentions:

   Midori: 31
   Go:     27
   C++:    27
   C:      18
   Rust:   10
   Swift:  03
   D:      02
   Scala:  02

None for Erlang! Could it be said that Joe Duffy is focussing on statically typed languages or systems programming languages? Interesting that Go is most referenced, not C++ :)