Around 2008 when that article was written was the peak of the hype of transactional memory. Many people thought it could be used by normal programmers placing atomic blocks around arbitrarily complex code using any data structures from the whole program. Some people even thought code could be in transactions by default all the time, committed with &#x27;commit&#x27; statements periodically.<p>That article should be read with that context in mind.<p>Now that transactional memory has fallen well out of fashion and people are being a bit more realistic I think it&#x27;s more likely it will be applied by experts as a kind of multi-word compare and swap, for implementing specific data structures with some support for composability. Which of course would still be a gain for software engineering.<p>This C++ work could support that kind of use-case.