3 ms·
"I think Google is making some bad choices with the technologies that they are choosing to support (Python/Java over Ruby, Mercurial over Git)." I remember a l
by riobard 18y ago
"I think Google is making some bad choices with the technologies that they are choosing to support (Python/Java over Ruby, Mercurial over Git)."
I remember a large portion of Google's codebase has been based on Python/Java when Ruby was not popular back then. How could you say they made a bad choice to support their own infrastructure? As the reason of choosing Mercurial for Google Code, consider the following facts in addition:
0. Mercurial is written in Python (well, some critical parts in C)
1. Google App Engine supports Python first (then Java)
2. GvR works in Google
3. Python adopts Mercurial this year for version control
- tvon 18y agoGood points, but as pointed out elsewhere in this thread: * Mercurial support at Google started before the discussion to move Python (I don't know details, but someone said it here so it must be true) * Google was using Python long before GvR was hired. [edit: s/hg/Mercurial/, I guess it's the proper thing to say]
- jasonwatkinspdx 18y agoThe road of convenience isn't necessarily the best road for your product. Looking at how github has exploded, and how much more momentum git has in the community, it's hard for me to be convinced that it's not worth the effort it would take google to support it. I also think they should support hg and bzr.