git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: Beau Martinez <beau@beaumartinez.com>, git@vger.kernel.org
Subject: Re: git add -p—splitting hunks, limit is too large
Date: Sun, 4 Sep 2016 10:10:25 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1609041001421.129229@virtualbox> (raw)
In-Reply-To: <20160902191425.ki7nfhlqgnihoqpw@sigill.intra.peff.net>

Hi Peff,

On Fri, 2 Sep 2016, Jeff King wrote:

> The good news (or maybe the bad) is that "add -p" is implemented
> entirely in Perl. :)

Yeah, you would definitely not call this "good news" if you were in my
shoes.

There is no question that it has grown way too unwieldy and that we (once
again, as with so many other scripts) missed the boat to convert it to C.

Scripting is nice for prototyping. But it comes at a high
portability/performance cost if taken too far. And we took it way too far.

Just look at all of those 1667 lines of git-add--interactive and weep. So
many things reimplemented in Perl instead of reusing functions in
libgit.a (or introducing them, making them usable from other parts of
Git). Wasted time is what I see there.

The worst part is that it completely violates our original "Unix
philosophy" of implementing the business logic in C and combinig it using
light-weight scripting.

And of course now the script is *so large* that nobody wants to undertake
the task of porting it to C.

Ciao,
Dscho

  parent reply	other threads:[~2016-09-04  8:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 14:36 git add -p—splitting hunks, limit is too large Beau Martinez
2016-09-02 19:14 ` Jeff King
2016-09-02 19:49   ` Christian Neukirchen
2016-09-04  8:10   ` Johannes Schindelin [this message]
2016-09-04  8:01 ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1609041001421.129229@virtualbox \
    --to=johannes.schindelin@gmx.de \
    --cc=beau@beaumartinez.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).