This is another view of the Clojure STM idea, from the Haskell camp:
http://channel9.msdn.com/Shows/Going+Deep/Programming-in-the-Age-of-Concurrency-Software-Transactional-Memory
Recently, we visited MSR Cambridge(UK) to meet some of the great minds
working there. In this case, we were fortunate enough to get an hour's
time with Simon Peyton-Jones
<http://research.microsoft.com/users/simonpj/> and Tim Harris
<http://research.microsoft.com/%7Etharris/>, who are researchers working
on a very hard problem: making it easier (more predictable, more
reliable, more composable) to write concurrent applications in this the
age of Concurrency (multi-core is a reality, not a dream).
Specifically, Simon and Tim (and team) are working on a programming
technology called Software Transactional Memory (STM) which provides an
elegant, easy to use language-level abstraction for writing concurrent
applications that is based on widely-understood conceptual constructs
like Atomic operations (and, well, Transactions...). Simon, Tim and team
do all the nasty locking work for you. With STM-enabled languages, you
can just concentrate on the algorithms at hand and leave the
low-level heavy lifting to the sub-system.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
