Re:Go channels, goroutines and GC available in Nim
by tatterdemalion on Monday June 01, 2015 @05:39PM
(#9642352)
"apps really end up needing the flexibility of shared memory"
Why? Just performance or is there a design reason also?
For different use cases Rust-style ownership semantics (when the performance of GC and runtime interoperability become an issue), or Azul-style pauseless GC (when you're willing to trade throughput for latency), or shared-nothing architectures (when you need them for legacy reasons like JavaScript, or want a simple programming model like Erlang) can work great.