David Terei wrote:
Good chance you've already read this but if not here is a good post by
Linus about his take on the problems with darcs:
http://markmail.org/message/vk3gf7ap5auxcxnb
I always have to smile at the complaint that something is academic. :D
You know, like purely functional
On Sat, 23 Apr 2011, Heinrich Apfelmus wrote:
David Terei wrote:
Good chance you've already read this but if not here is a good post by
Linus about his take on the problems with darcs:
http://markmail.org/message/vk3gf7ap5auxcxnb
I always have to smile at the complaint that something is
On Sat, 2011-04-23 at 12:31 +0200, Heinrich Apfelmus wrote:
David Terei wrote:
Good chance you've already read this but if not here is a good post by
Linus about his take on the problems with darcs:
http://markmail.org/message/vk3gf7ap5auxcxnb
I always have to smile at the complaint
On 21/04/2011 11:16 PM, John Millikin wrote:
My chief complaint is that it's built on patch theory, which is
ill-defined and doesn't seem particularly useful. The
Bazaar/Git/Mercurial DAG model is much easier to understand and work with.
Possibly as a consequence of its shaky foundation, Darcs
I'm a great fan of darcs, and also have never run into the performance and
reliability issues that GHC has. That said, it's clear that they *have* run
into them, and if something else makes GHC development go more smoothly,
then I'm 100% supportive of their using it.
It is disappointing, though
On 04/22/11 01:34 AM, Maciej Marcin Piechotka wrote:
On Thu, 2011-04-21 at 21:29 +0100, Andrew Coppin wrote:
I'm sure this must be a VFAQ, but... There seems to be universal
agreement that Darcs is a nice idea, but is unsuitable for real
projects. Even GHC keeps talking about getting rid of
Jason Dagit schrieb:
* Every commit needs --ask-deps , because the automatic
dependency detector can only detect automatic changes (and not
things like adding a new function in a different module)
You mean it can only detect dependencies that depend on each
Maciej I believe the biggest problem was (i.e. when migration started)
Maciej that there is no big-name-hosting supporting darcs. When
Maciej code.haskell.org went down people were cut off from code.
Please forgive me if the answer is obvious : is Darcs storage backend
agnostic, or must it
Good chance you've already read this but if not here is a good post by
Linus about his take on the problems with darcs:
http://markmail.org/message/vk3gf7ap5auxcxnb
I personally think he is right on the money here. The other problem
with Darcs is performance. While it has improved a lot its
On Thu, 2011-04-21 at 19:39 -0500, Jake McArthur wrote:
On Thu, Apr 21, 2011 at 7:31 PM, Maciej Marcin Piechotka
uzytkown...@gmail.com wrote:
Last time I checked it disallowed my as 5 depended on 4 which depended
on 3 which depended on 2 which depended on 1 as all changed x.hs
Merely
On 4/21/11 10:16 PM, wren ng thornton wrote:
rather, what I'd like is someplace to keep my code which also provides a
good bugtracker. Unfortunately, neither darcsden nor patchtag offer
darcsden does include a simple issue tracker now.
___
On 4/22/11 11:39 AM, Simon Michael wrote:
On 4/21/11 10:16 PM, wren ng thornton wrote:
rather, what I'd like is someplace to keep my code which also provides a
good bugtracker. Unfortunately, neither darcsden nor patchtag offer
darcsden does include a simple issue tracker now.
Ah,
I'm sure this must be a VFAQ, but... There seems to be universal
agreement that Darcs is a nice idea, but is unsuitable for real
projects. Even GHC keeps talking about getting rid of Darcs. Can anybody
tell me what the problems with Darcs actually are?
On Thu, Apr 21, 2011 at 1:29 PM, Andrew Coppin
andrewcop...@btinternet.comwrote:
I'm sure this must be a VFAQ, but... There seems to be universal agreement
that Darcs is a nice idea, but is unsuitable for real projects. Even GHC
keeps talking about getting rid of Darcs. Can anybody tell me
My chief complaint is that it's built on patch theory, which is
ill-defined and doesn't seem particularly useful. The Bazaar/Git/Mercurial
DAG model is much easier to understand and work with.
Possibly as a consequence of its shaky foundation, Darcs is much slower than
the competition -- this
On Thu, Apr 21, 2011 at 7:16 PM, John Millikin jmilli...@gmail.com wrote:
My chief complaint is that it's built on patch theory, which is
ill-defined and doesn't seem particularly useful. The Bazaar/Git/Mercurial
DAG model is much easier to understand and work with.
For me its greatest asset
Andrew Coppin wrote:
I'm sure this must be a VFAQ, but... There seems to be universal
agreement that Darcs is a nice idea, but is unsuitable for real
projects.
I not sure what constitues a real project, but I have found
Darcs to be more than satisfactory for Ben Lippmeier's DDC
compiler
John Millikin wrote:
My chief complaint is that it's built on patch theory, which is
ill-defined and doesn't seem particularly useful. The Bazaar/Git/Mercurial
DAG model is much easier to understand and work with.
Possibly as a consequence of its shaky foundation, Darcs is much slower
On Thu, Apr 21, 2011 at 3:29 PM, Andrew Coppin
andrewcop...@btinternet.com wrote:
I'm sure this must be a VFAQ, but... There seems to be universal agreement
that Darcs is a nice idea, but is unsuitable for real projects. Even GHC
keeps talking about getting rid of Darcs. Can anybody tell me
Um, the patch theory is what makes darcs just work. There is no need
to understand it any more than you have to know VLSI design to
understand how your computer works. The end result is that darcs
repositories don't get corrupted and the order you integrate patches
doesn't affect things meaning
On Thu, 2011-04-21 at 16:16 -0700, John Meacham wrote:
Um, the patch theory is what makes darcs just work. There is no need
to understand it any more than you have to know VLSI design to
understand how your computer works. The end result is that darcs
repositories don't get corrupted and the
On Thu, 2011-04-21 at 21:29 +0100, Andrew Coppin wrote:
I'm sure this must be a VFAQ, but... There seems to be universal
agreement that Darcs is a nice idea, but is unsuitable for real
projects. Even GHC keeps talking about getting rid of Darcs. Can anybody
tell me what the problems with
On Thu, Apr 21, 2011 at 6:32 PM, Maciej Marcin Piechotka
uzytkown...@gmail.com wrote:
Assume following changes
1. Feature X - file x.hs
2. Feature Y - file y.hs and x.hs
3. Feature Z - file z.hs and x.hs
4. Fix to feature Y (changes x.hs)
5. Fix to feature X (changes x.hs)
Now before
On Thu, 2011-04-21 at 19:19 -0500, Jake McArthur wrote:
On Thu, Apr 21, 2011 at 6:32 PM, Maciej Marcin Piechotka
uzytkown...@gmail.com wrote:
Assume following changes
1. Feature X - file x.hs
2. Feature Y - file y.hs and x.hs
3. Feature Z - file z.hs and x.hs
4. Fix to feature Y
On Thu, Apr 21, 2011 at 7:31 PM, Maciej Marcin Piechotka
uzytkown...@gmail.com wrote:
Last time I checked it disallowed my as 5 depended on 4 which depended
on 3 which depended on 2 which depended on 1 as all changed x.hs
Merely changing the same file is not sufficient for that. In order for
+1 to what you said.
On 4/21/11 4:16 PM, John Meacham wrote:
Incidentally, I wrote a github like site based around darcs a few
years ago at codehole.org. It is just used internally by me for
certain projects. but if people were interested, I could resume work
on it and make it public.
John,
Codehole doesn't sound like a good name. Don't lose stuff in codehole!
Sent from my iPhone
On Apr 21, 2011, at 7:33 PM, Simon Michael si...@joyful.com wrote:
+1 to what you said.
On 4/21/11 4:16 PM, John Meacham wrote:
Incidentally, I wrote a github like site based around darcs a few
On Thursday, April 21, 2011 4:16:07 PM UTC-7, John Meacham wrote:
Um, the patch theory is what makes darcs just work. There is no need
to understand it any more than you have to know VLSI design to
understand how your computer works. The end result is that darcs
repositories don't get
On Thu, Apr 21, 2011 at 8:42 PM, John Millikin jmilli...@gmail.com wrote:
On Thursday, April 21, 2011 4:16:07 PM UTC-7, John Meacham wrote:
Um, the patch theory is what makes darcs just work. There is no need
to understand it any more than you have to know VLSI design to
understand how your
On 4/21/11 10:33 PM, Simon Michael wrote:
+1 to what you said.
On 4/21/11 4:16 PM, John Meacham wrote:
Incidentally, I wrote a github like site based around darcs a few
years ago at codehole.org. It is just used internally by me for
certain projects. but if people were interested, I could
30 matches
Mail list logo
