5 ms·

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.

by fructa 14y ago

lamby 14y ago
If anything, it was avoided because Git was not in Python.. But yeah.
- lloeki 14y ago
  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-other-dvcss http://www.python.org/dev/peps/pep-0374/#why-mercurial-over-...
  - jnoller 14y ago
    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.
    - lloeki 14y ago
      > 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/DjangoSuccessStoryBitbucket https://code.djangoproject.com/wiki/DjangoSuccessStoryBitbuc...
- lucian1900 14y ago
  Especially since hg exists, is extremely similar to Git and arguably has a better UI.
senthilnayagam 14y ago
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.html http://www.tiobe.com/index.php/content/paperinfo/tpci/index.... https://github.com/languages 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
- deleted 14y ago
  [deleted]

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.

by fructa 14y ago

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.

lamby 14y ago

If anything, it was avoided because Git was not in Python.. But yeah.

lloeki 14y ago
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-other-dvcss http://www.python.org/dev/peps/pep-0374/#why-mercurial-over-...
- jnoller 14y ago
  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.
  - lloeki 14y ago
    > 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/DjangoSuccessStoryBitbucket https://code.djangoproject.com/wiki/DjangoSuccessStoryBitbuc...
lucian1900 14y ago
Especially since hg exists, is extremely similar to Git and arguably has a better UI.

senthilnayagam 14y ago

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.html http://www.tiobe.com/index.php/content/paperinfo/tpci/index.... https://github.com/languages 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

deleted 14y ago
[deleted]