'. '

TransactionalMemory

From APIDesign

(Difference between revisions)
Jump to: navigation, search
Current revision (09:43, 14 September 2019) (edit) (undo)
(New URL for Joe's weblog)
 
Line 1: Line 1:
-
[[TransactionalMemory]] is an attempt to bring the power of databases to general purpose programming languages. [[wikipedia:Transactional Memory]] should be the ultimate source of information, however it seems that much better understanding of [[TransactionalMemory]] can be obtained by reading follwing [http://www.bluebytesoftware.com/blog/2010/01/03/ABriefRetrospectiveOnTransactionalMemory.aspx practitioner's report]. Joe Duffy's text is worth reading - it shows why weak [[TransactionalMemory]] cannot work. In the process of showing that it describes the gory details that remain unnoticed in the general overview at [[wikipedia:Transactional Memory]].
+
[[TransactionalMemory]] is an attempt to bring the power of databases to general purpose programming languages. [[wikipedia:Transactional Memory]] should be the ultimate source of information, however it seems that much better understanding of [[TransactionalMemory]] can be obtained by reading follwing [http://joeduffyblog.com/2010/01/03/a-brief-retrospective-on-transactional-memory/ practitioner's report]. Joe Duffy's text is worth reading - it shows why weak [[TransactionalMemory]] cannot work. In the process of showing that it describes the gory details that remain unnoticed in the general overview at [[wikipedia:Transactional Memory]].
-
As far as I can tell Joe's [http://www.bluebytesoftware.com/blog/2010/01/03/ABriefRetrospectiveOnTransactionalMemory.aspx write up] is one of the best texts on internet I have read in months. It is deep, detailed, informative, entertaining and contains pieces of wisdom you don't want to miss. Like the ''"these kinds of moments make me a believer in formal computer science"'' acknowledgement.
+
As far as I can tell Joe's [http://joeduffyblog.com/2010/01/03/a-brief-retrospective-on-transactional-memory/ write up] is one of the best texts on internet I have read in months. It is deep, detailed, informative, entertaining and contains pieces of wisdom you don't want to miss. Like the ''"these kinds of moments make me a believer in formal computer science"'' acknowledgement.
-
A more meta-level thought: Joe's [http://www.bluebytesoftware.com/blog/2010/01/03/ABriefRetrospectiveOnTransactionalMemory.aspx text] shows why it is important to properly document failures. Why it is important to describe roads that lead nowhere. As [[wikipedia:Jára_Cimrman|Jára Cimrman]] says: Should not we value the person who tried to blow a cigarette smoke into watter to find out that this process does not produce gold? Thanks Joe for showing us that (weak) [[TransactionalMemory]] does not help to build reliable programming environment.
+
A more meta-level thought: Joe's [http://joeduffyblog.com/2010/01/03/a-brief-retrospective-on-transactional-memory/ text] shows why it is important to properly document failures. Why it is important to describe roads that lead nowhere. As [[wikipedia:Jára_Cimrman|Jára Cimrman]] says: Should not we value the person who tried to blow a cigarette smoke into watter to find out that this process does not produce gold? Thanks Joe for showing us that (weak) [[TransactionalMemory]] does not help to build reliable programming environment.

Current revision

TransactionalMemory is an attempt to bring the power of databases to general purpose programming languages. wikipedia:Transactional Memory should be the ultimate source of information, however it seems that much better understanding of TransactionalMemory can be obtained by reading follwing practitioner's report. Joe Duffy's text is worth reading - it shows why weak TransactionalMemory cannot work. In the process of showing that it describes the gory details that remain unnoticed in the general overview at wikipedia:Transactional Memory.

As far as I can tell Joe's write up is one of the best texts on internet I have read in months. It is deep, detailed, informative, entertaining and contains pieces of wisdom you don't want to miss. Like the "these kinds of moments make me a believer in formal computer science" acknowledgement.

A more meta-level thought: Joe's text shows why it is important to properly document failures. Why it is important to describe roads that lead nowhere. As Jára Cimrman says: Should not we value the person who tried to blow a cigarette smoke into watter to find out that this process does not produce gold? Thanks Joe for showing us that (weak) TransactionalMemory does not help to build reliable programming environment.

Personal tools
buy