Hacker News Reader

Comment by jphackworth | Hacker News Reader

It's great to hear that Django is moving to GitHub. It seems like the Python community has been slow to adopt git, perhaps because Bazaar and Mercurial are written in Python, and perhaps because GitHub uses Ruby. That said, it seems like git is emerging as the winner, and IMHO GitHub is far superior to anything available outside of git, so I'm glad they're making the move.

View on HN

> It seems like the Python community has been slow to adopt git, perhaps because Bazaar and Mercurial are written in Python, and perhaps because GitHub uses Ruby.

For a lot of people in the Python world, choosing a DVCS just means picking what CPython picked (hg). At the time, that decision was at least partly due to the fact that git had poor Windows support, and less about the languages involved (GitHub/Ruby weren't a factor anyway since it would be a self-hosted git install).

If the decision was to be made again today, most people I've talked to think git would be the choice.

My experience is still that git is at best a second class citizen on windows, in terms of installation, performance and usability.

Is this no longer the case in some way?

I can't really speak to performance (I don't have any large projects where I could tell a difference), but the install is painless, and the windows git shell is really nice.

windows git performance on a 300KLOC, 8000+ file C++ project was IME very good - and that was 2-3 years ago. compared with g++, it was great.

I've been using msysgit at work for the past couple of years, and it works fine. There's a bit of an impedance mismatch between the command line orientation of git and the crippled command line experience on Windows, but msysgit comes with its own mini bash implementation, complete with ls, vi and a few other handy utilities.

heh, I myself started using HG partly because of language patriotism, partly because Bitbucket (running on Django) had a better offer than Github. yet one had to be out of his mind not to like Django moving to any of those providers. it's a great step. (a little tiny bit sad they didn't choose hg/bitbucket ;))

the move surprised me a bit, AFAIR when this topic (moving to a DVCS) was raised on DjangoCons, Russel explained that's not a priority (correct me if my memory fails).

I don't want to put words in his mouth, but I would imagine Adrian's list of priorities represents just that -- the things he wants to work on.

Yes, that, plus the things that I think would be good for the framework and the community.

oh, great :)

forgot to link the hn post in comments on your blog, glad you came here so fast. cheerz

Indeed, this is good news - there have always been a pull request or two on the Django GitHub mirror that would need to be closed and redirected to the Django project bug tracker, where they would need to generate a patch. This always slowed contributions and made people who genuinely wanted to help jump through needless hoops.

Reply on news.ycombinator.com