MacRuby is moving to Github(lists.macosforge.org)
lists.macosforge.org
MacRuby is moving to Github
http://lists.macosforge.org/pipermail/macruby-devel/2011-March/007418.html
4 comments
Hmm, is that really a problem? https://github.com/macruby/macruby is working as expected. I assume you would just type the camel case name once, when cloning the repository.
Case sensitivity on a file system is generally retarded. I think it was an accidental 'feature' of some file systems and now in order to be compatible everyone has to do it. Real world benefit is zero while the annoyance factor is high. Not counting lost productivity due to case related bugs....
Yes, this is irritating, not unlike the RedCloth gem.
The fact that it's 2011 and only just now is MacRuby moving to git is a good reminder that getting stuff done doesn't require all the new shiny tools, and other bleeding edge accouterments.
Edit: my point was that sometimes keeping your focus on your problem, not your tools, yields the most gains.
Edit: my point was that sometimes keeping your focus on your problem, not your tools, yields the most gains.
I don't think this is so much about SVN vs Git, I think it's more about bringing MacRuby development to where the center of Ruby development attention is.
More people will click around new source commits and become inspired to make their own contributions.
More people will click around new source commits and become inspired to make their own contributions.
Chrome puts the dot in the URL, so clicking from the email posting goes to https://github.com/MacRuby/MacRuby. instead of https://github.com/MacRuby/MacRuby
That's not chrome, it's the source of the page:
<A HREF="https://github.com/MacRuby/MacRuby.>https://github.com/M...;
<A HREF="https://github.com/MacRuby/MacRuby.>https://github.com/M...;
Upps.. My poor user's view. Should've clicked view source
Hope this give the project more attention, because MacRuby is pretty good!
And now, in the interests of looking a Git horse in the mouth: it's a shame about the CamelCase in the organisation and repository names. Not many people do this on GitHub; for example, GitHub's own organisation name is "github", not "GitHub", even though the company name is ordinarily written in camel case.
Stretching out before me is a grim meathook future of repeatedly typing "macruby/macruby", then seeing "ERROR: macruby/macruby.git doesn't exist", then saying GOD DAMMIT, then retyping it with the caps.