Well, advertising for the win right?
Was looking up a song I vaguely remembered via youtube, and I noticed that > 30% of the search results are taken up by a single advert for a film (Liam Neeson in Taken, ironically) which sits at the top right, leaving the rest of the column blank.
What the git vs bzr discussion is about IMO is usability. The following blog post about DTrace on linux talks about the same issue, and I’d like to use Bryan’s words:
“Over and over again, we made architectural and technical design decisions that would yield an instrumentation framework that would be not just safe, powerful and flexible, but also usable. The subtle bit here is that many of those decisions were not at the surface of the system (where the discussion on the Linux list seems to be currently mired), but in its guts.”
“Over and over again, we made architectural and technical design decisions that would yield a Distributed VCS be not just safe, powerful and flexible, but also usable. The subtle bit here is that many of those decisions were not at the surface of the system (where the discussions going on at the moment seem to be currently mired), but in its guts.”
I keep running into folk whom I knew of, that use bzr, but I did not know that they use bzr.
Right now there is a lot of discussion going on about DVCS in various projects. While I imagine most bzr users just want to get on with their coding (after all thats what bzr is good at :))… it would be fantastic if you could blog that you use it, and folk at GUADEC wear the T-shirt!
Also, I’m at GUADEC, and I’m extremely happy to answer questions from anyone, bzr user, git user, or even svn user :)
Well, the gauntlet is down (BTW – desktop power integration. Cool!). The use case Ted talks about is actually quite interesting – we were at UDS last month, waiting on a SVN server that was apparently so slow we could have walked to it and copied stuff onto harddisk more quickly. (Really. No kidding). bzr was idling and blocked on network IO the whole time… kudos for the plugin Ted!
For my response, may I present a new index format, (branch url) 70% smaller than bzr’s current default, equally fast at most workloads, up to 20 times faster at others. I started this this week, and John jumped in in overlapping time periods, but I think it counts!
Note that the perfromance wins are a component improvement – other things we haven’t addressed yet can make the index improvements less visible. But several early adopters have told me that they see a 25-30% reduction in ‘time bzr log > /dev/null’ or other commands.
bzr branch http://bazaar.launchpad.net/~lifeless/+junk/bzr-index2 ~/.bazaar/plugins/index2
bzr branch https://bazaar.launchpad.net/~jameinel/+junk/pybloom ~/.bazaar/plugins/pybloom
cd <repository you want to experiment on>
bzr upgrade –btree-plain
(or –btree-rich-root for bzr-svn users).
A version of this will be going to trunk soon, and it will be able to upgrade from any repository that you have that uses the plugin as long as you keep the plugin installed.