The comparison is written in terms of Go vs C/.NET. The interesting thing is that it isn’t actually stated that they dumped the BEAM (silently implied maybe).
And to be realistic they’ve probably gone mainstream by standardizing on a container management system that lets them shift workloads to external commodity servers. So fault tolerance and reliability have to be approached completely differently.
The question is whether there is a niche for the BEAM in the cloud space where container management systems are the norm. From $erverless to Elixir makes me hopeful but it is a fair question whether the same effect could have been just as easily accomplished with Go.
I still think the BEAM will be relevant in the resource constrained IoT space.
