On Fri, 7 Jun 2013, Ramkumar Ramachandra wrote:
> Johannes Schindelin wrote:
> > My initial reaction, too. It was hard enough to get Perl included with Git
> > for Windows (because of that pesky Subversion dependency).
> Nevertheless, we had to do it, and we did it.
That is not quite correct. *I* did it. Not *we*. And I will not do it
> We will do it again, if we get enough important code written in Ruby.
I am a bit bored by this hypothetical talk. This hypothetical "we will do
it again", to be precise. Given my experience, it would be very painful if
"enough important code" was written in Ruby. Nobody would help me "do it
again". Just like nobody helps right now to upgrade to a newer Perl. Feel
free to prove me wrong. Until that time, I will firmly believe that there
is no "we will do it again".
So here is a chance to prevent that: not repeat the mistake, and stay away
from language hell by avoiding to require yet another language.
> > As you can see from the commit history, I was the primary force behind
> > trying to get everything "core" in Git away from requiring scripting
> > languages (I think it is an awesome thing to provide APIs for as many
> > languages as possible, but a not-so-cool thing to use more than one
> > language in the core code). It does not seem that anybody picked up
> > that task when I left, though.
> Rewriting everything in C? Is anyone bored enough to pick up this task?
> Bourne shell is a great language for prototyping; git-rebase.sh (and
> friends), git-stash.sh, git-pull.sh are doing just fine. Sure, it makes
> sense to do heavy-lifting in C, and this is happening as it has always
> been happening (remember git-commit.sh?). If you followed the list
> emails, you'd know that Felipe is looking into delegating large portions
> of the work done by git-rebase.sh to sequencer.c.
As you know, there are very good reasons why I do not follow those mails.
> Anyway, all this talk about some hypothetical ideas just bores me.
> What matters is what is currently happening. And nobody is actively
> rewriting the "core in Git" in C, so I don't see the point of
> discussing anything but patches.
Exactly. Nobody really cares about keeping Git portable enough. Hence my
impression that this idea to start requiring yet another language for core
parts of Git is a bit misguided, and only logical from the point of view:
"If you don't like it, why don't you install Linux?" (which, just in case
you wondered, is a pretty naive way of looking at the real world).
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html