News for hackers. Stuff that matters.
Re:Django is now (officially) on GitHub by senthilnayagam on Saturday April 28, 2012 @02:21AM (#3902202)
good to see django on github

hey dowvoters i am not a troll, many python projects avoided github initially because github was powered by ruby, see it in context chef, puppet,vagrant,heroku are of ruby origin but now loved by people from various technology backgrounds

Re:Django is now (officially) on GitHub by detst on Saturday April 28, 2012 @03:08AM (#3902267)
I didn't see your original comment but if it was just "good to see django on github", you were downvoted for not adding anything to the conversation. Your edit is better.
Re:Django is now (officially) on GitHub by fructa on Saturday April 28, 2012 @03:50AM (#3902332)
Your conjecture that GitHub was initially avoided by people who don't use Ruby because it's written in Ruby is pointlessly divisive and quite silly.
Re:Django is now (officially) on GitHub by lamby on Saturday April 28, 2012 @05:08AM (#3902469)
If anything, it was avoided because Git was not in Python.. But yeah.
Re:Django is now (officially) on GitHub by lloeki on Saturday April 28, 2012 @05:37AM (#3902510)
From PEP-0374 [0]:

> Lastly, all things being equal (which they are not as shown by the previous two issues), it is preferable to use and support a tool written in Python and not one written in C and shell.

Okay this pertains to Python itself but could easily have mattered to Django.

[0] http://www.python.org/dev/peps/pep-0374/#why-mercurial-over-...

Re:Django is now (officially) on GitHub by jnoller on Saturday April 28, 2012 @07:00AM (#3902653)
Note that this is python-core - which has an obvious python bias for a variety of reasons, and also doesn't pertain in any way to github (see the fact they self-host HG). In actuality, having HG be written in python has helped python-core write plugins and resolve other issues.

So; in summation pick the right tool for your team not due to some techno bigotry, which is what that PEP outlines.

Re:Django is now (officially) on GitHub by lloeki on Saturday April 28, 2012 @08:28AM (#3902785)
> in summation pick the right tool for your team

Precisely and I was not saying otherwise. The Python team chose hg partly (but not only) because it is written with Python, just as the Django team could have decided to choose Bitbucket partly because it is written with Django[0]. And they could have chosen hg partly because it is written with python, or chosen git (which they did), as both were supported by Bitbucket.

Whatever, I'm not saying they should have, just that they could, and that dogfooding is a valid point if it is not blindly overrated (i.e bigotry) but carefully considered.

[0] https://code.djangoproject.com/wiki/DjangoSuccessStoryBitbuc...

Re:Django is now (officially) on GitHub by lucian1900 on Saturday April 28, 2012 @06:45AM (#3902625)
Especially since hg exists, is extremely similar to Git and arguably has a better UI.
Re:Django is now (officially) on GitHub by senthilnayagam on Saturday April 28, 2012 @04:16PM (#3903963)
I don't have any damning evidence to win a lawsuit :) but would still make a attempt to give empirical evidence

Tiobe 2012 report http://www.tiobe.com/index.php/content/paperinfo/tpci/index....

https://github.com/languages

Javascript is 9th and Ruby in 11th for popularity on tiobe but take first and second rank on github open source projects

I understand not all pre-github projects have moved from sourceforge and google code, but even for newer projects people have biases for technology choices

Re:Django is now (officially) on GitHub by human_error on Saturday April 28, 2012 @08:25AM (#3902782)
> many python projects avoided github initially because github was powered by ruby

This doesn't make any sense. Don't tell me that there are C# developers who don't use Google because they use Java.

Re:Django is now (officially) on GitHub by streptomycin on Saturday April 28, 2012 @11:53AM (#3903239)
It would make sense a little bit if GitHub was open source.