Live data from Hacker News

The future of programming languages in a massively concurrent world

news.ycombinator.com

31–33 of 33 posts

Re: The future of programming languages in a massively concurrent world

#31
post #28

I'm surprised the decent solution to this isn't more widely known. People have mentioned Occam and Stackless Python; both interesting. But their ancester is Hoare's CSP and other descendant have included Squeak (not the Smalltalk relation), Newsqueak, Plan 9's Alef, Inferno's Limbo, and now libthread. Channels with co-operating threads are easy to reason about. See Russ Cox's overview page http://swtch.com/~rsc/threa…

Stackless python does absolutely nothing to help with scaling applications to multiple cores. It allows you to write asynchronous applications to better utilize a single processor for operations that depend heavily on IO (or otherwise waiting for some resource).

I wasn't pushing Stackless, just saying that others have mentioned it and its ancestory has something in common with what I'm trying to sell; channels as a synchronisation method. See the references I gave for more details.

Re: The future of programming languages in a massively concurrent world

#32

Occam. Specifically, http://transterpreter.org Yes, the language it runs (Occam) is 20 years old. But the language was designed for programs running on dozens to thousands of nodes, and in the transterpreter implementation, there's the possibility of doing this on heterogeneous hardware, where the fast nodes do things like splitting and merging the data set, and the smaller "grunt compute" nodes do the actual work. P…

Occam is yet another thing with its roots in Hoare's CSP. See my posts elsewhere on this story.
Post reply on HN