Software Transactional Memory
is no longer a pipe dream or the stuff of academics.
STM.NET, as it's called, is ready for your experimentation
The goal of STM.NET is to be able to exploit concurrency by using components written by experts and consumed by application programmers who can then compose together these components using STM. Transactional memory provides an easy-to-use mechanism to do this
safely. STM.NET is of course not a concurrency silver bullet and this is an experimental rrelease of the .NET Framework that allows C# programmers to try out this technology, specifically a particular implementation of STM.
The STM team really
needs your feedback to understand if they're doing the right things to meet your needs. Traditionally, using STM for simple trasactional tasks didn't make sense. The overhead was too high. Is this still the case? What needed to
change in the .NET Framework to enable STM.NET? Remember, this is a .NET Framework
experiment to enable STM for managed code.
Here, we meet most of the team responsible for STM.NET: Chris Dern, Yossi Levanoni, Sasha Dadiomov, Weirong Zhu, Sukhdeep Sodhi and Lingli Zhang
Tune in, meet the team and get a good sense of what this very small team has accomplished with STM.NET and learn about some of the paths taken to get there. This represents really great engineering. Congratulations to the STM team! Now, Niners, go get the