[macintux]

> Yes, the concurrency is great, but it is concurrency you would probably not need if the code executed faster in the first place.

If you're using Erlang concurrency for performance you're probably doing it wrong.

[freedomben]

Well, it depends on the bottleneck. CPU-bound code, I would of course agree. For I/O bound though, especially network I/o with variable peers (which is the vast majority of code written nowadays) erlang's concurrency model is fantastic.

Also worth mentioning is that you can write CPU intensive code in rust and invoke it as NIFs[1]

[1] https://github.com/rusterlium/rustler