Dave Rolsky wrote:
> On Thu, 16 Sep 2004, Eric S. Raymond wrote:
>
>> John Peacock <jpeacock@rowman.com>:
>>> Is this a subtle bias because
>>> it is written in Perl using the Perl bindings to Subversion or a more
>>> direct criticism of the use of custom attributes to store merge points?
>>
>> I can't speak for anyone else here, but I regard both those traits
>> as being kludgy.
>>
>> I think svk is a clever idea, but I would prefer to see support for
>> decentralized development integrated into the subversion core and done
>
> I don't really see this as terribly likely.
>
> Storing merge history will be in the subversion core in the future,
> according to the project's todo list. But the developers have been pretty
> clear that decentralized version control is not one of the their main
> goals.
Correct - but "not a main goal" is not the same as "go away, we don't want
it even if well designed and coded". I'm only 1 opinion, but I don't see any
reason why certain core svk-alike features couldn't migrate into subversion
itself eventually.
>> in a cleaner way. At the very least I'd be happier if the svk-equivalent
>> stuff were in Python, which I think has better long-term maintainability.
>
> So basically you have no meaningful criticism here, you just want to start
> a language war. Good idea. Then we can fight about emacs vs. vim
> afterwards!
>
> Seriously, _you_ might be happier if it were in Python, but other people
> wouldn't be. Who cares? Unless you plan to write an SVK-alike in Python
> what's the point of bringing this up?
Well said.
Although (IMO) it's easier to write unmaintainable code in Perl, it's
possible to write Perl which is just as maintainable as Python, given a bit
of discipline.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 17 01:42:20 2004