8 ms·
Google Code now supports Mercurial
- durin42 18y agoI particularly like their DAG grapher: http://code.google.com/p/erratic/source/list http://code.google.com/p/erratic/source/list Something about the curved corners leaves me really pleased with how it looks.
- mattculbreth 18y ago<ducking while the Git fans prepare to flame>
- johnbender 18y agoI was going to start rawring but this made me laugh. Still odd they chose to support Mercurial first. Maybe it's used internally more that git is?
- pohl 18y agoThey document their tradeoff analysis here: http://code.google.com/p/support/wiki/DVCSAnalysis http://code.google.com/p/support/wiki/DVCSAnalysis
- mbrubeck 18y agoGoogle mainly uses Perforce internally. They do use git for their external Android repository (with automatic imports from their internal Perforce branches).
- stevejohnson 18y agoWhile I am a huge Git fan, I completely understand their decision to go with Mercurial. It has better documentation, better cross-platform support, and a similar feature set. Git is improving in all these areas, and I use Git for my personal projects, but Mercurial does have its advantages.
- iamelgringo 18y agoPython's move to Hg might have been an influence as well. Mssr. vRossum does work for GOOG after all.
- tonfa 18y agoWell the google code support was started long time before Python started looking for a DVCS. If one had an influence on the other it was probably the other way round.
- ubernostrum 18y agoI wouldn't count on it. Internally Google uses Perforce for version control (and IIRC git for some public-facing things), and it's been noted that Google's Python style rules and procedures are quite different from Guido's (their style guide actually goes against PEP 8 -- easy way to spot open-source contributions from Googlers, though).
- marcusbooster 18y agoIn all honesty, I bet the GitHub folks are ecstatic over this decision.
- jhawk28 18y agoLooks like the main reason for the choice was efficient HTTP support.
- charlesju 18y agoI think Google is making some bad choices with the technologies that they are choosing to support (Python/Java over Ruby, Mercurial over Git). While there might be technological advantages to Python/Java/Mercurial, the Ruby and Git communities are a more evangelical and willing to try new things.
- dschobel 18y agoAre you being facetious or do you really believe evangelism trumps technology?
- deleted 18y ago[deleted]
- jshen 18y agoI'd say that it plays a much greater role than people want to believe.
- andreyf 18y agoI think GvR working at Python has something to do with it. If, instead, Yukihiro Matsumoto had gone to work at Google and build a team developing development technologies around Ruby, things might be different. Not that it's that big of a change either way.
- jmtulloss 18y agoThere is something to be said for the fact that Google went after GvR and not YM.
- jasonwatkinspdx 18y agoYay for one line insinuations about people few of us actually know well enough to have an informed opinion about.
- 18y ago
- jakozaur 18y agoIt seems that Google did a good job implementing mercurial on its own infrastructure. It could encourage open source developers to switch from subversion to hg.
- dchest 18y agoThey doesn't get it. It's not about just public repository hosting anymore -- it's about "social networking" for code. I know, this sounds like hype for anyone except those who used GitHub (or, maybe, BitBucket, but I haven't used it). It's different than just hosting projects.
- jcdreads 18y agoDisclaimer: I use Git for my own stuff and as an svn client at work. But I wonder if Git's author's boorish-yet-sort-of-amusing behavior when invited to speak at Google a couple of years ago may have also quietly weighed on the decision some: http://www.youtube.com/watch?v=4XpnKHJAok8 http://www.youtube.com/watch?v=4XpnKHJAok8