It'll be therapeutic.
[EMAIL PROTECTED] (Greg A. Woods):
> [EMAIL PROTECTED] wrote:
> >
> >
> > Let me ask: what is it about locking and concurrency
> > that makes them mutually exclusive?
>
> What is it about them that is not mutually exclusive?!?!?!?
If it weren't for the seemingly-earnest excessive InteraBangs, this
would seem like a deliberate attempt to misunderstand/misrepresent
what other people are posting. That's probably a good strategy if you
think of yourself as some kind of CVS immune system in charge of
warding off potential contributors who might threaten the ancient
wisdom given to you by the FoundingCoders(tm), god rest their carpal
tunnels.
Then again, maybe you genuinely didn't "get it", so here's a
completely unambiguous phrasing: "What is it about locking and
concurrency that makes supporting both policies in the same
tool -- but not necessarily on the same file at the same
time -- mutually exclusive?"
Does your parser barf on that? I'm trying to create a little
understanding of each other. Help me out here.
> > Why not let the repository maintainer choose their policy?
>
> The can -- it just means chosing between CVS and some other tool
That's one alternative. Forking is another. Neither is as cool
as cooperating with an extant tool's community. "Why bother," Kate
asked. Well, she answered it herself: CVS does concurrency mostly
right.
Mostly. I mean no offense to the guardians of the secret meaning
of the letter 'C' here, but I see CVS as a fixer-upper. I think
that supporting concurrency to the exclusion of other policies
as a design flaw. Apparently I'm not alone here because I walked
into a room where everybody has been talking this issue into the
ground.
I wonder how many potential contributors have turned away with
this fundamentalist stance. I don't have any more free spare time
per week that the 5 that Tobias mentioned. But I've heard of this
amazing open-source idea where people pool their free time and
come up with things much greater than any one of them could have
accomplished. The problem with the model is that if you guard the
source code with enough belligerent trolls it kind of destroys
any hope of a community atmosphere and your fruit withers on the
vine, much like the stagnancy that is CVS.
So sad. I love this tool and would rather not have to say goodbye.
