Buffer Overflow; Core Dump

Originally published at Improved Means for Achieving Deteriorated Ends. You can comment here or there.

Wow. I have been thinking about The Concurrency Problem waaaayyy too much the last 48 hours or so. I’m coming around about STM and am really hoping I get an e-mail back from Tim Sweeney answering some questions I had. Yes, that Tim Sweeney.

All the same, I’d rather Erlang or some other message passing functional+concurrent programming model get adopted than a non message-passing model such as Haskell. Erlang just seems cleaner to me. I just like it a bit better. Perhaps that will all change as I actually start trying to write code with them (Erlang, Haskell). Anyone who feels like coming along and writing something better that has the advantages of both without the disadvantages of either feel free. What I’m trying to say is, feel free to invent NBL.

Okay, here’s what I’ve been reading:
http://www.algorithm.com.au/talks/concurrency-erlang/
http://patricklogan.blogspot.com/
http://patricklogan.blogspot.com/2007_02_04_patricklogan_archive.html
http://lambda-the-ultimate.org/node/1277
http://lambda-the-ultimate.org/node/2048#comment-25151
http://www.tbray.org/ongoing/When/200x/2007/06/07/Concurrency
http://enfranchisedmind.com/blog/archive/2007/08/13/323
http://enfranchisedmind.com/blog/archive/2007/02/08/191
http://www.dehora.net/journal/2007/08/phat_data.html
http://tech.puredanger.com/2007/08/14/concurrency-terracotta/
http://www.cincomsmalltalk.com/userblogs/ralph/blogView?showComments=true&printTitle=Erlang,_the_next_Java&entry=3364027251
http://www.defmacro.org/ramblings/concurrency.html
http://yarivsblog.com/articles/2006/08/16/why-erlang-is-a-great-language-for-concurrent-programming
And of course, the thing that started it all:
http://www.gotw.ca/publications/concurrency-ddj.htm