I dunno about SVK as I've never used it. I was talking about Subversion, abbreviated svn on the command line.
Sorry to everybody for perhaps touching a nerve; I really was just desiring to "lower the bar" to Haskell newbies that the book might attract. It's hard enough coming from an imperative background and learning the concepts, syntax, and semantics of Haskell without having to also learn a new SCM tool. That, and I find Subversion / CVS ubiquitous in the corporations (that you would recognize the names of) in which I've contracted over the last 13 years (obviously cvs until svn came along). On 5/29/07, Hakim Cassimally <[EMAIL PROTECTED]> wrote:
On 29/05/07, Jules Bean <[EMAIL PROTECTED]> wrote: > Doug Kirk wrote: > > No offense to the darcs creators, but > > > > 1) Only current Haskellers use it; everyone else either uses > > Subversion or is migrating to it; > > > If that is true, then they have missed the point. DVC is a real win for > most workflows. > > The applicable alternatives to darcs are : bzr, git, mercurial, tla. > They have different pros and cons which are discussed at length on > various blogs. > > svn just doesn't make the list; it's not a comparable project, because > it's centralised. SVK is more plausible but since it is essentially a > hack to implement decentralisation on top of centralisation, it has > different design constraints than things designed from the bottom-up as > decentralised. How do the differing design constraints make svk not comparable? As far as I understood it, it's a decentralised version control system that happens to layer over a very popular existing system, and which therefore gets some of its goodies like working over http. osfameron _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
