Systems Programming in Distributed, Multicore World with Go, Rust, and Parasail

This article pops up every so often, so again I should emphasize that the concurrency story in Rust has changed greatly in the interim (and will continue to change as new approaches to concurrency are fleshed out in the stdlib).

Here is a video of a talk the author, Tucker Taft, gave about the ParaSail language at Mozilla last year:<p><a href="https://air.mozilla.org/region-based-storage-management-parasailing-without-a-garbage-chute/" rel="nofollow">https:&#x2F;&#x2F;air.mozilla.org&#x2F;region-based-storage-management-para...</a>

Seems like this is a better source of the article: <a href="http://parasail-programming-language.blogspot.com/2013/04/systems-programming-with-go-rust-and.html" rel="nofollow">http:&#x2F;&#x2F;parasail-programming-language.blogspot.com&#x2F;2013&#x2F;04&#x2F;sy...</a>

Unfortunately, it&#x27;s a &quot;why X is great, by the vendors of X&quot; article. It&#x27;s an ad for ParaSail, which is too new (and possibly too weird) to have much traction yet.

Note that the document seems to be from the spring of last year.<p>I think it is interesting that Parasail has no explicit pointers and only uses value semantics. This means that no garbage collection is needed: the storage associated with a variable is freed when the variable goes out of scope, or when the variables value is set to <i>null</i> (and yes, you must have a value of type Optional T in order to set it to null). I thought that having pure value-semantics would be too costly in a language, but apparently that kind of solution has its place after all.