Bitkeeper, the universe, and everything
Posted Feb 24, 2004 19:20 UTC (Tue) by
lm (guest, #6402)
In reply to:
Bitkeeper, the universe, and everything by dh
Parent article:
subversion 1.0 is released
Hi Dirk,
I can't do the comparison to Arch objectively because we produce a product with a similar model.
I suspect, however, that an objective comparison would come up with things like:
-
BK is 6 years old and has fulltime talented staff working on it. Hence it is more mature, better docs, better platform support, etc.
-
BK scales better. Try and import 38,000 changesets in Arch and watch what happens. That's not to say that BK is zippy, it needs be better, but it can at handle the kernel in the free version and upcoming commercial versions are much faster.
-
BK merges better, both automerges and hand merges.
-
BK is easier to use. We add a new user who syncs with bkbits.net every 45 minutes. More than 50,000 users have figured out how to use BK without ever talking to us. I've designed and built two different SCM systems, I'm well versed in at least 8 others, and I have a tough time with Arch. SVN wins that battle hands down.
-
BK has far more infrastructure built up in it to handle all those little tasks that come up when doing SCM things. BK can import/export CVS trees, for example. One customer said "we rolled out BK and threw away the 6,000 lines of perl we had wrapped around CVS, BK does all that". I can't emphasize this point enough. We can all argue which model is better in theory but even if you have the perfect model there are 1000 details that have to be handled that have nothing to do with the model.
-
Better testing. 1/4th of the BK source base is regressions. We run regressions on all platforms all the time, it's a huge stability win.
-
Better platform support. We support Windows, MacOS, all the BSD/Linux and commercial Unux platforms equally.
-
GUIs. We have some pretty pleasant GUIs and they are getting better, see bkexplorer for example. Not exactly eye candy but it gets the job done. And we offer Visual Studio integration, etc.
-
More workflows. See this description of
using BK on a submarine or this talk
on various BK workflows.
-
Infrastructure you can use. We have a free hosting service at
bkbits.net which hosts the kernel, mysql and a pile of other projects. No ads, no nonsense, just a place to put your stuff. And it's a ton faster than sourceforge.
-
Business model. We have a business model that pays for BK development. No outside investors, hence no stupid business decisions which hurt the end users. Contrast with Arch where the primary developer is forced to beg for handouts or SVN where HP paid for the development. You may or may not like our model but SCM tools are annoyingly complex (it took SVN 3.5 years to get to a CVS clone) and you need some development effort that isn't going away.
Personally, I am starting to think it is great that Arch et al exist. They get people away from the licensing discussions and get them focussed on the model. We like the distributed model, it clearly works better, and if you have to use open source tools we'd rather have you learning about the model we think is better.
The difference between Arch and BK is going to be a lot like the difference between GCC and Microsoft's compiler. I just timed compiling BK on windows with gcc vs Microsoft's compiler: 10m41s vs 4m40s. They both do the same thing at some level, one just works better. You pays your money and takes your choice and the old adage you get what you pay for still applies.
(
Log in to post comments)