There is nothing parallel about a web server by the way. It's all about concurrency.
And the Erlang and Go approach have significant overheads that are unacceptable for a system programming language. You can't use either Erlang or Go for **parallel** problems such as those from high-performance computing. Erlang actors are just unsuited for this. Go requires a different calling convention making calls to C (or Fortran) significantly more expensive, which would force use to basically not use all the C code lying around as we would be way slower. Furthermore Goroutines are littered with syscalls that just thrashes CPU caches with kernel data. > The low-level primitives could be the same, but how those low-level building > blocks are used make the end result different. Erlang or Go somehow execute > simple blocking code in an efficient parallel way. Freeing humans from hard > work of using state machines and thread-pools explicitly :) There is nothing preventing Nim for providing such but time and people ready to implement this. Unfortunately Nim doesn't have a worldwide company with unlimited resources (Telecom or Google) to push that everyday. Nim is still very much enthusiasts driven.
