Comments on: I Have Seen the Future, and It is Copy-On-Write http://hackerboss.com/i-have-seen-the-future-and-it-is-copy-on-write/ Developing software and managing development teams. Sat, 21 Jan 2012 06:56:39 +0000 http://wordpress.org/?v= hourly 1 By: Copy on Write « IT Primerhttp://hackerboss.com/i-have-seen-the-future-and-it-is-copy-on-write/comment-page-1/#comment-7070 Copy on Write « IT Primer Tue, 06 Sep 2011 03:09:47 +0000 http://hackerboss.com/?p=365#comment-7070 [...] Hacker Boss [...] [...] Hacker Boss [...]

]]> By: Vladimir Sedachhttp://hackerboss.com/i-have-seen-the-future-and-it-is-copy-on-write/comment-page-1/#comment-6659 Vladimir Sedach Fri, 12 Aug 2011 20:32:53 +0000 http://hackerboss.com/?p=365#comment-6659 The first person to apply the idea of multiple versions to concurrency control was David Reed in his 1978 PhD dissertation (http://publications.csail.mit.edu/lcs/specpub.php?id=773), inventing what's now known as MVCC. It's been popular in databases since the 80s.Henry Baker has a good summary of other things this idea has been used for in one of his papers (http://home.pipeline.com/~hbaker1/TreeShadow.html section 7).Overall the "purely functional" data structure is an obvious idea from the lambda calculus, and predates Turing machines and von Neumann's work and any kind of programming language. It's just the fault of limited machine resources that it isn't the default way programs are thought about. The first person to apply the idea of multiple versions to concurrency control was David Reed in his 1978 PhD dissertation (http://publications.csail.mit.edu/lcs/specpub.php?id=773), inventing what’s now known as MVCC. It’s been popular in databases since the 80s.

Henry Baker has a good summary of other things this idea has been used for in one of his papers (http://home.pipeline.com/~hbaker1/TreeShadow.html section 7).

Overall the “purely functional” data structure is an obvious idea from the lambda calculus, and predates Turing machines and von Neumann’s work and any kind of programming language. It’s just the fault of limited machine resources that it isn’t the default way programs are thought about.

]]> By: Ville Laurikarihttp://hackerboss.com/i-have-seen-the-future-and-it-is-copy-on-write/comment-page-1/#comment-110 Ville Laurikari Tue, 21 Jul 2009 10:15:19 +0000 http://hackerboss.com/?p=365#comment-110 Yep, Clojure is really, really cool. It even has built-in support for software transactional memory. If it only had very efficient automatically disk-backed data structures, Clojure would be near perfect. Yep, Clojure is really, really cool. It even has built-in support for software transactional memory. If it only had very efficient automatically disk-backed data structures, Clojure would be near perfect.

]]> By: Nikhttp://hackerboss.com/i-have-seen-the-future-and-it-is-copy-on-write/comment-page-1/#comment-109 Nik Tue, 21 Jul 2009 10:05:34 +0000 http://hackerboss.com/?p=365#comment-109 Just a note, you've probably seen it already, Clojure (<a href="http://clojure.org/" rel="nofollow">http://clojure.org/</a>) seems to have some of the Copy-on-Write features described in this article. Just a note, you’ve probably seen it already, Clojure (http://clojure.org/) seems to have some of the Copy-on-Write features described in this article.

]]>