On Fri, Mar 13, 2015 at 6:45 AM, Russel Winder via Digitalmars-d < digitalmars-d@puremagic.com> wrote:
> The removal of shared memory multi-threading in favour of using > processes and channels should never be underestimated as a Really Good > Thing™ that other native code languages (*) have failed to do anything > about. Thus Go wins, others lose. > Except that Go does not really remove shared memory multithreading; it is still possible to get data races (which is why they have a race detector). They provide channels, but nothing is preventing races other than convention. On the other hand, Rust (a native code language) offers a much superior solution, with compile-time enforcement of data sharing. -- Ziad
