From: Dan Kegel <dank@kegel.com>
To: linux-kernel@vger.kernel.org
Subject: Re: BK is *evil* corporate software [was Re: New BK License Problem?]
Date: Wed, 09 Oct 2002 17:37:22 -0700 [thread overview]
Message-ID: <3DA4CBC2.DA1A4A68@kegel.com> (raw)
Larry McVoy <lm@bitmover.com> wrote:
> if you have 3-5 developers there is no reason to not use CVS,
> it works well enough. ...
> OK, now let's look at it as you grow. Most of our customers are in the
> 25-100 developer range. They move very quickly and have lots of parallelism
> in the code. So things like work flow and merging are critical, if that
> doesn't work, the whole team slows down. Let's say we have a 60 seat sale.
> That's $90K/year for BK. Let's say the engineers cost $100K/each (it
> may be lower where you are but it's more like $180-220 here when you add
> in building/mgmt/all the other overhead). So that's $6M/year in engineers.
> The BK cost is 1.5% of that. You say that your guys are $50K/year? OK,
> so we're at 3% of that. The point is that if BK makes your team 3% more
> productive, it costs zero.
>
> And none of that includes the hardware costs, which are dramatically
> cheaper for BK, it works on a laptop. Clearcase doesn't.
Larry is spot on. I evaluated Clearcase, Bitkeeper, and Perforce
recently
for an 80 developer shop currently suffering with SourceSafe.
Clearcase was ridiculously expensive and complex; I would never use it.
Bitkeeper appeared to have *exactly* the features we wanted,
and the price was not out of our range. We eventually settled on trying
Perforce for a while because we know it could do most of what we needed,
but it was a really tough call. Larry took the time to make sure we
understood the issues, and I have a lot of respect for him.
Anyone who says Larry is evil is smoking crack. He's good people.
- Dan
next reply other threads:[~2002-10-10 0:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 0:37 Dan Kegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 20:55 New BK License Problem? tom_gall
2002-10-04 21:08 ` Larry McVoy
2002-10-05 17:54 ` Ben Collins
2002-10-05 18:25 ` Larry McVoy
2002-10-06 22:11 ` BK is *evil* corporate software [was Re: New BK License Problem?] Pavel Machek
2002-10-07 18:51 ` Mike Galbraith
2002-10-07 21:31 ` Larry McVoy
2002-10-09 23:34 ` Henning P. Schmiedehausen
2002-10-09 23:55 ` Larry McVoy
2002-10-10 3:50 ` Mark Mielke
2002-10-10 4:16 ` Derek D. Martin
2002-10-10 4:56 ` Mark Mielke
2002-10-10 7:33 ` Jirka David
2002-10-10 7:26 ` Rogier Wolff
2002-10-10 13:36 ` Larry McVoy
2002-10-10 14:04 ` yodaiken
2002-10-10 16:14 ` Henning P. Schmiedehausen
2002-10-10 16:25 ` Jeff Garzik
2002-10-10 16:52 ` Richard B. Johnson
2002-10-10 17:28 ` Alan Cox
2002-10-10 16:38 ` Larry McVoy
2002-10-10 18:57 ` Eli Carter
2002-10-10 19:01 ` Larry McVoy
2002-10-10 0:03 ` Jamie Lokier
2002-10-10 7:31 ` Rogier Wolff
2002-10-07 18:56 ` tom_gall
2002-10-07 20:44 ` Pavel Machek
2002-10-07 20:55 ` Rik van Riel
2002-10-07 21:36 ` Alexander Viro
2002-10-07 20:30 ` Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DA4CBC2.DA1A4A68@kegel.com \
--to=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.