You seem sure like them that JS is not good. They didn't even bother to consider it as a choice!
If you wanted to point to their evidence you couldn't because they don't have any.
I'm suggesting that JS is not good for every possible use. And that is ok.
I would not want a core internet router or a kernel to be implemented in JS. But I am happy it is used elsewhere.
It was already in "JS". It was ported to Go.
The case against JS was specific: data marshalling neglects the Web Workers performance boost for an "embarrassingly parallelizable" project. And it was stated clearly.