Ask HN: Who's using bzr for version control?
I see a lot of push behind git and to a lesser degree, hg. However, bzr remains the read-headed stepchild of the DVCS world. Why?
Because git is simple in its basic structure I feel like I can understand what's going on. With bzr/hg/svn, I just have no idea what's going on, I have no idea what the tool means by words like "checkout" and "revert" and "update"; they're just too vague.
git has a too-steep learning curve and is just cryptic and hostile.
svn is too intolerant of slight mistakes, leading to difficult-to-fix situations, and merges don't work very well.
We tried both at my day job, and are now very happy on bzr. I also found it really nice for my single-developer spare-time project.
P.S. Let me know if somebody's going to build a "BzrHub".
for a while, google used hg.
what high profile project uses bzr and advertises it?
I know the response sounds like a chicken-egg problem, and it is. To gain traction, a prolific company or project needs to use bzr.