csdigiOP•

I remember how amazed I was when I first encountered STM in my undergraduate. I thought I would put it out there as an interesting concurrency paradigm, and to see if anyone has thoughts on its implications in languages with Side-Effects (Haskell has it limited to an STM monad). The papers and conferences on STM are generally really interesting, although it dosent hurt that Simon Peyton-Jones is a great speaker.

1
tty2awesome creator•

I definitely like the Haskell implementation of STM. The idea of bringing it to C++ is pretty cool to me as well. Great video!

1
csdigiOP•

I often wonder if it would be possible to bring a subset of the STM functionality to python using a decorator class around some methods for transactions, although there is an obvious reason it to SPJ a weekend to hack STM support into GHC when the challenge seems insurmountable in every other language.

1
fuckwaddle•

Haskell and Clojure have ugly, horrible STM implementations.

The overhead is ridiculous and they use locks under the surface, so it's not "optimistic" concurrency at all. The blocks can endlessly retry.

-1
smackmybishop•

I thought the whole point was to hide the locks from the user while still allowing composable concurrent transactions. Do you know of a good STM implementation?

1
BrainInAJar•

too bad UltraSPARC-RK is dead. Hardware transactional memory would be a fantastic thing to have

1
muleaga•

well that's one badass shirt.

-5