3 ms·
When your server has to do some computations to return results. Erlang is bad at that.
by yelnatz 10y ago
When your server has to do some computations to return results.
Erlang is bad at that.
- PeCaN 10y agoSuch as what exactly? "Computations to return results" is rather generic, to say the least (and, if ‘computations’ includes handling requests, something that servers tend to always do).
- sudhirj 10y agoC is best at problems that are CPU and memory bound, Go can handle problems that are CPU bound-ish and goroutines help with IO bound problems. Erlang handles problems that are MASSIVELY IO bound.
- davidw 10y agoI think it's fairer to say that "Go is better at that". "Bad" depends on the user and their needs. In some cases, Go is "bad" at that too and you should use C. In that case, you could always connect the C code to either Go or Erlang, although that introduces complexity into the system you're creating.