News for hackers. Stuff that matters.
Re:Why and How I Switched from Python to Erlang by steveklabnik on Thursday July 07, 2016 @10:28AM (#12049514)

  > In the language and/or the standard library?
In Rust, we have extremely strong concurrency support in the language/standard library in the form of our type system, which disallows data races at compile time. We only provide 1:1 threading, but libraries can use this type system to extend it: there's N:M threading libraries, as well as more exotic concurrency stuff than we provide directly. Rust also generally takes a "no batteries included" approach, generally speaking.

In Ruby, there's Thread and Fiber. MRI's GIL hurts it here, but other implementations don't have this problem.

Re:Why and How I Switched from Python to Erlang by ngrilly on Thursday July 07, 2016 @05:39PM (#12052249)
Can you provide links to the Rust N:M threading libraries you recommend? How is the stack managed in these libraries (does it start small and is resized at runtime)?

Same question for Ruby :-)

Re:Why and How I Switched from Python to Erlang by steveklabnik on Thursday July 07, 2016 @07:26PM (#12052736)