2 ms·
That was poorly written. And amazingly, the author neglected to shed light as to why Erlang has a more a 'complete' story in regards to distributed f/t systems
by eternalban 9y ago
That was poorly written. And amazingly, the author neglected to shed light as to why Erlang has a more a 'complete' story in regards to distributed f/t systems ("reliability", "concurrency").
Erlang has OTP, Go does not. Erlang is FP, Go is not. These are the critical differences.
Silver lining (in context of OTP) for Go is that the du jour 'cloud' based architectures will provide the OTP like capabilities ("elastic", "fail-over", etc.) for deployed (micro-)services. It seems that in the (future) long-term, Go is better positioned than Erlang for cloud based systems.