True, and as long as he was still using it that was a valid argument of his. But it took him and a few others only a few weeks to code a replacement that everyone seems to be even happier with functionality-wise. So while it's clear that BK was a better fit than any of the other existing SCMs, I think I have to agree with the people on lkml who were saying it would have been better to put energies (or incentive) into developing a free alternative in the first place. Just think of all the developer time wasted on flame-wars ;-).

Aside: without knowing either of them personally, I think that particular quote was given to save Larry McVoy (who's a friend of Linus AFAIK) some face.

And the fact that Linus was happy with Bitkeeper doesn't change anything about the danger of keeping one's important data in a proprietary format which is only accessible through a proprietary product. Sure, one should always use the tool that best fits the job, but when part of the job description is "I want to be able to access my data any time in the future, regardless of what happens with a certain vendor/product", programs like Bitkeepet fail the spec.


Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan

In reply to Re^2: Linux kernel Bitkeeper mess (seriously OT) by tirwhan
in thread Learning How to Use CVS for Personal Perl Coding Practices by neversaint

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.