> Performance comes second. I want to state that performance is too generalize here. BEAM VM also have a goal of low latency which can be consider as performa

> Performance comes second. I want to state that performance is too generalize here. BEAM VM also have a goal of low latency which can be consider as performance. I'm not entirely sure if GO is aiming for that or not. I would never do any numerical stuff on BEAM though, it's very slow. This article is a bit dated but is interesting between Go and Erlang: https://www.theerlangelist.com/article/reducing_maximum_latency https://www.theerlangelist.com/article/reducing_maximum_late...