[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: darcs vs tla

From: Stephen J. Turnbull
Subject: Re: [Gnu-arch-users] Re: darcs vs tla
Date: Mon, 08 Nov 2004 21:03:59 +0900
User-agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.5 (chayote, linux)

>>>>> "Catalin" == Catalin Marinas <address@hidden> writes:

    Catalin> A second problem I think is Haskell. Not so many people
    Catalin> can help with coding

Haskell is no harder than Lisp in principle, and if you'll go back in
this list a bit you'll find a thread on Lisp and parentheses where
asuffield makes a really convincing case (to me, anyway) that
Haskell's presentation with minimal parentheses plus the "offsides
rule" is far more readable than Lisp.  I think it's reasonable to
suppose that people who want to help with darcs can learn enough
Haskell to do so.

    Catalin> and it is also much slower than C or C++.  The today's
    Catalin> compilers are not smart enough to optimally deal with
    Catalin> pure functional languages.

Please confirm it's possible to compile darcs, and which compiler you
used.  I heard recently that darcs is strongly dependent on Hugs98,
which is an interpreter.  Seemed a little odd (Haskell98 is a
well-defined language, and Hugs doesn't have all that much in the way
of extensions), but that's what I heard.

    Catalin> While darcs is a nice research project, my recommendation
    Catalin> would be to stay with arch, at least until you hear
    Catalin> somebody happily using darcs with a huge source tree like
    Catalin> the Linux kernel.

I wouldn't go so far as that, but certainly I'd say to investigate
experience with a tree 3X as big as your current one, to give room to
grow while darcs does!

Institute of Policy and Planning Sciences
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]