Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I started out with bzr-git a long time ago for small one-off projects where I wasn't getting too deep into the process. Well, that's not true, when I First dug into DVCS, I tried all three, and since I was on windows back then (all-linux, now), git failed early, as since it didn't have a native windows version. Later on, when I didn't necessarily have time to learn git due to short deadlines, I tried bzr-git a few times.

I don't have _real_ answer, besides that it doesn't "feel right" to use another tool on a git repo. I _want_ to know git better. It's just not very easy to learn without fully committing to it.

As for bzr, there have definitely been speed improvements in the past couple years. I can't say how much faster, as I'm used to it. The Only times I notice things running slowly are when branching a large remote repo for the first time and when my system is completely maxed (currently working on a dynamic video-generation project). Otherwise, I barely notice. And besides, how often does one actually wait for a return prompt when checking in? `bzr ci -m "whatever"` and alt-tab back to whatever I'm working on.

* editing for clarification



Well, I prefer to work in vim, so the speed with which my VCS does things is pretty important. Other than that, screw it, I just switched back to bzr. Both hg and bzr have very good git interoperability, so now I can use whichever of the three VCSes I like, even for the same working tree (I can have .git, .hg and .bzr in the same working tree, all updated, and push whichever I like).

I'm already enjoying bzr again, though. I also would like to learn git, but I have a startup to launch, and I don't think git is worth the (pretty big) effort at this stage.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: