NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in <199911192358.PAA24109@kiev.wall.org>
Did I say I expect Perl to do the right thing? :-)
--Larry Wall in <199911200217.SAA24898@kiev.wall.org>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Interesting (Score:2)
That's the second hard-to-reproduce bug I heard with Subversion the past few weeks (this one being the first [perl.org]). I've never ran into such problems with Subversion - it just works, so it seems very strange to me. If you can somehow reproduce the problematic behaviour on non-confidential, example repositories than I'm sure the Subversion developers will appreciate a bug report.
Complaining is easy, but actually fixing the problems is more worthwhile in the long run.
Re:Interesting (Score:2)
Why should I put time and energy into fixing a bad technology that, if I have the chance, I'll never use again? OK, so that's a bit unfair, but frankly, I just don't care about Subversion any more. It's that simple. I know that in future positions I'll likely be working on projects where management/developers are too timid to switch to something better than Subversion, so yes, I should care how well it works, but if I could reproduce this problem in the first place, I might actually know what caused it and simply not do it again.
Subversion isn't broken because it has a few bugs. Subversion is like an old 386 machine I used to work on. It's quaint and I have some lingering fondness for it as it was the had the first GUI I ever used, but I wouldn't want to do serious work on it.
Reply to This
Parent