I can agree with most of these points. Some more things to consider: - Git is 20x faster than Hg (that's 99% of the reason I switched and hate using Darcs) - People attached to Hg can use Hg-Git; I've used it several times with nice results. It can also be used to easily convert Hg repos to Git (I was using it to maintain a Pygments mirror, but got bored) - GitHub is much nicer than BitBucket. I usually look for a git mirror of a BitBucket repo since I hate browsing on BB - Even Plan9Port moved from Hg to GitHub a few days ago - Some Google devs even host their projects on GitHub (not Google Code) Thank goodness no one has mentioned CodePlex. BTW, I frown on projects that choose something largely inferior over a better choice just because "one is written in X language." Now, if python.org was written in Ruby, that would just be sad, but certain things just don't matter. Like DVCS's. Guido van Rossum <guido at python.org> wrote: >On Sat, Nov 22, 2014 at 10:49 PM, Nick Coghlan <ncoghlan at gmail.com> >wrote: > >> More generally, I'm very, very disappointed to see folks so willing >to >> abandon fellow community members for the sake of following the crowd. >> Perhaps we should all just abandon Python and learn Ruby or >JavaScript >> because they're better at getting press in Silicon Valley? > > >That's a really low blow, Nick. > >I think these are the facts: > >- Hg/Git are equivalent in functionality (at least to the extent that >the >difference can't be used to force a decision), and ditto for >BitBucket/GitHub, with one crucial exception (see below) > >- We're currently using Hg for most projects under the PSF umbrella >(however, there's https://github.com/python/pythondotorg) > >- Moving from Hg to Git is a fair amount of one-time work (converting >repos) and is inconvenient to core devs who aren't already used to Git >(learning a new workflow) > >- Most newer third-party projects are already on GitHub > >- GitHub is way more popular than BitBucket and slated for long-term >success > >But here's the kicker for me: **A DVCS repo is a social network, so it >matters in a functional way what everyone else is using.** > >So I give you that if you want a quick move into the modern world, >while >keeping the older generation of core devs happy (not counting myself >:-), >BitBucket has the lowest cost of entry. But I strongly believe that if >we >want to do the right thing for the long term, we should switch to >GitHub. I >promise you that once the pain of the switch is over you will feel much >better about it. I am also convinced that we'll get more contributions >this >way. > >Note: I am not (yet) proposing we switch CPython itself. Switching it >would >be a lot of work, and it is specifically out of scope for this >discussion. > >-- >--Guido van Rossum (python.org/~guido) > > >------------------------------------------------------------------------ > >_______________________________________________ >Python-Dev mailing list >Python-Dev at python.org >https://mail.python.org/mailman/listinfo/python-dev >Unsubscribe: >https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Check out my website: http://kirbyfan64.github.io/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20141123/7d2714f3/attachment-0001.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4