========> Today, Eric S Raymond <Eric> wrote:
Eric> I get a little nervous when I hear "Perl" in a context like
Eric> this. I used to write a lot of Perl, but have almost
Eric> completely abondoned the language. The problem I have is
Eric> that Perl is a maintainability disaster, very nearly a
Eric> write-only language at program sizes over a few hundred
Eric> lines.
The following are also strictly my opinions.
The projects I was involved have shown, that you _can_ write such
unmaintanable code in Perl. But when you design (rather than just go
on and start hacking) a Perl application, using the build in OO
mechanisms and package concepts, you can write very modular and clear
code. I think that this holds for most programming languages.
Eric> Again, strictly my opinion...but if you think you could do a
Eric> cvsweb equivalent, I'd sure rather see you do that first.
The working areas I mentioned are just ideas where I could help. I
don't claim for me to be able to sit down and write such a program in
an evening ;-)
Eric> Finally (and the real reason I spoke up), Emacs already
Eric> includes a generic version-control client with an interface
Eric> many people have in their fingers. Would you consider
Eric> writing a Subversion back-end for Emacs VC mode?
IMHO, VC is only good for handling _one_ file at a time (and for
_that_ purpose it's incomparable practical). But when it comes to
commit a bunch of changes or to just get an overview of the working
tree, I usually prefer pcl-cvs. It would be very nice to have both
tools for SVN. I don't know if they are already in work by someone,
but this an area where I'm interested in and where I would like to
help.
--
Jens Klöcker <jens@kloecker.org> | Co-existence or no existence.
Received on Sat Oct 21 14:36:24 2006