Now, I’ve never really felt like ReviewBoard was competing with Smart Bear Software’s Code Collaborator. I’m sure they see it that way, but it doesn’t have any bearing on the way we’ve run the project. We’re not concerned about feature checklists or keeping parity; we’ve been trying to make Review Board be the best tool we can for us, and all of our contributors have been doing the same. Comparisons to other tools rarely factor into the equation, since we don’t have a lot invested in whether people choose us or another. The way I view it, any sort of code review tool is a step in the right direction.
That said, this competitive analysis published on their web site had me giggling. The sheer amount of FUD and outright lies is staggering. My favorite bit is how Review Board doesn’t support pre-commit reviews for Perforce (which was the first thing it supported).
#1 by Baz on December 9th, 2008
Quote
I especially liked how they mark you as ‘No’ for ‘Has a user manual’, then quote from this nonexistent user manual — twice — as evidence for other problems???
#2 by Aaron Seigo on December 9th, 2008
Quote
We use Review Board in the Plasma project. It’s been a very nice asset. So first off; thanks. =)
As a small suggestion: instead of beiing smug and all “oh, they did-uh-nt!” respond with a list of the “no“s that are “yes“s, the “no“s that soon will be, etc. That’ll get a lot further.
#3 by David Trowbridge on December 10th, 2008
Quote
I honestly don’t care whether they’re accurate or not. I know I personally don’t expect any company to compare their products to their competitors in an accurate way. And as I said, I don’t have a lot invested in whether people use Review Board or go with something else. One thing I do realize is that a lot of people want a tool with paid support backing it–that’s not something we can offer, so it’s a very legitimate reason to choose something else.
I’m mostly smug because it amuses me. That’s the big point of the post
#4 by Mikkel Kamstrup Erlandsen on December 10th, 2008
Quote
Hehe… Browsing the comparisons with the other code review products listed at the Smart Bear site leaves me with one possible conclusion:
* Code Collaborator implements a truckload of features no one else deems important
Each and every app they compare them selves to are more or less ticked in red on (almost) _all_ points of comparison. To be fair I never really tried any of the products mentioned…
#5 by marc0s on December 10th, 2008
Quote
Also, they say that there is no User Manual for Review Board, and in another point they quote it…
#6 by Gregg Sporar on December 11th, 2008
Quote
We created that comparison page because people would ask us: “How does Code Collaborator compare to ReviewBoard?” Our intent was not to be misleading or spread FUD. In fact, when others have pointed out inaccurate information in other comparisons, we have happily updated the entries, so perhaps we are different than other companies when it comes to product comparisons.
I have already fixed the (embarrassing) typo about the ReviewBoard user manual. Over the next few weeks I want to improve the matrix further (by clarifying the Perforce pre-commit issue, for example), but not surprisingly I am much more familiar with Code Collaborator than I am with ReviewBoard. It would be great if you could provide additional specific examples of where you think ReviewBoard is not represented fairly. I would really appreciate it if you would post that to your blog or send it to me in an email (gregg dot sporar at smartbear dot com). Thanks.
#7 by Dan Savilonis on December 17th, 2008
Quote
It seems they conveniently left out all distributed version control systems from the list of supported ones.
#8 by Jason Cohen on December 24th, 2008
Quote
@Dan: Actually we support git and mercurial and quite a few of our customers are already using it.
We haven’t announced *official* support because we’d like to add a few more features and do more testing.
In fact, if you visit our feed back site (http://feedback.codecollab.com) you’ll see that those are the most requested features and that we’re actively working on it.