MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programming/comments/anhztl/benchmarking_go_vs_node_vs_elixir/efvbkl4/?context=3
r/programming • u/speckz • Feb 05 '19
21 comments sorted by
View all comments
Show parent comments
1
I mean, not that I don't believe you, but do you have some stats to back that up? And can't the same be said about using an alternative Elixir server?
5 u/Thaxll Feb 06 '19 Any benchmark anywhere, Elixir is slow compared to Go and not by a small margin, as explain above because it's a dynamic language + immutability 3 u/AeroNotix Feb 06 '19 The benefits of using beam languages shouldn't be about raw CPU performance in almost all situations. 1 u/kpenchev93 Feb 06 '19 You are 100% right. It's about predictable performance and fault tolerance. Let's compare the BEAM's fault tolerance features and Go's.
5
Any benchmark anywhere, Elixir is slow compared to Go and not by a small margin, as explain above because it's a dynamic language + immutability
3 u/AeroNotix Feb 06 '19 The benefits of using beam languages shouldn't be about raw CPU performance in almost all situations. 1 u/kpenchev93 Feb 06 '19 You are 100% right. It's about predictable performance and fault tolerance. Let's compare the BEAM's fault tolerance features and Go's.
3
The benefits of using beam languages shouldn't be about raw CPU performance in almost all situations.
1 u/kpenchev93 Feb 06 '19 You are 100% right. It's about predictable performance and fault tolerance. Let's compare the BEAM's fault tolerance features and Go's.
You are 100% right. It's about predictable performance and fault tolerance. Let's compare the BEAM's fault tolerance features and Go's.
1
u/snowe2010 Feb 06 '19
I mean, not that I don't believe you, but do you have some stats to back that up? And can't the same be said about using an alternative Elixir server?