Concurrency is achieved via async await. For parallelism each thread has its own GC so that makes things a lot safer, but sadly less efficient if your algorithm wants to share data between threads a lot (you can copy data between threads). You can also allocate shared memory but that's considered unsafe, this will hopefully be improved in the future.
As for how well this all works, well, I recently implemented a high performance parallel HTTP server [1]. It's currently hosting the Nim Forum[2] and has been doing so for the past few months. Also it's proving very performant[3].
1 - https://github.com/dom96/httpbeast
2 - http://forum.nim-lang.org/
3 - https://www.techempower.com/benchmarks/#section=test&runid=b...
Re:Nim partners with Status.im
by michaelsbradley on Tuesday August 07, 2018 @10:10PM
(#17712676)
It would be amazing if Pony Lang's[+] concurrency model could be realized in Nim, or if Nim could be extended as a language to optionally and cleanly support it. That's easier said than done, of course, since Pony's concurrency model is deeply wedded to its type system ("reference capabilities").
[+] https://www.ponylang.org/discover/#what-makes-pony-different
Many thanks for the detailed answer & ref.links.
Re:Nim partners with Status.im
by spooneybarger on Tuesday August 07, 2018 @08:53PM
(#17712305)
We are still going strong in Pony land. There an ebb and flow to publicly seen development.
Re:Nim partners with Status.im
by mcintyre1994 on Wednesday August 08, 2018 @08:02AM
(#17715140)
The writing style in your documentation is awesome! I haven't come across Pony before but it looks really nice, definitely going to give it a try. :)
I am still eyeballing Pony-lang for it's design choices, but development seems to have slowed down there.