Bazaar considered harmful

The documentation of Bazaar^[1] states that Bazaar is slower than Git, has fewer features than Git, takes up more space than Git, is not as well documented as Git, is only used by newbies, and so on. It even says they don't believe Bazaar could be more successful than other SCM systems.

Clearly the Bazaar documentation must have been written by someone who is forced to use Bazaar but secretly loves Git.

_____
^{[1] http://doc.bazaar.canonical.com/migration/en/why-switch-to-bazaar.html}

>>12
How do large studios handle this?
They use Perforce—a system designed to solve these problems rather than create them.  If you try to sell them on any open-source junk, you get at most a pat on the head and an ice cream cone.

How do real-world developers share code when there isn't a master repository?
They create a master repository, then share code with it.

>>12
How do I store art resources?
% git add

when there isn't a master repository?
Amend this now.  What the hell.

because in days of googling, not only does no one have an answer to this question, it seems no one has even considered it a problem
No-one has an answer, because no-one asks the question. No-one asks the question, because the answer is obvious.

>>15
mdickie quality!

>>12
Troll, but I'll bite.

Do they just share their repository over LAN and pull from eachother?

Yes, exactly! Or they set up a computer on the LAN to be a server, just like you would in SVN, and then push and pull from that, just like you "checkout" and "checkin" things with traditional SCMs, only they're pulling and pushing multiple commits to the master server at a time. It's not hard.


$ git clone ssh://192.168.1.76/product.git
$ cd product
$ make changes
$ git commit -a -m description of changes
$ git push
Password:
$ pause for some time
$ git pull
git tells you what changes have been made to which files
$ more changes
$ git commit -a -m another commit description
$ git push
Password:
$ done!


Just look how simple that is!