Re: Python extension commands in git - request for policy change
- From
- Patrick Donnelly <batrick@batbytes.com>
- Date
- Dec 12, 2012, 07:11 UTC
- Message-ID
- <CACh33Fpk8_ZXw8Ladx83J+rmdRYf7ruYAMMkqOKcoH3OApKPJQ@mail.gmail.com>
- In-Reply-To
- <20121212033043.GA24937@thyrsus.com>
Hi Eric,
On Tue, Dec 11, 2012 at 10:30 PM, Eric S. Raymond <esr@thyrsus.com> wrote:
Show 5 quoted lines
> It might be a good fit for extending git; I wouldn't be very surprised if > that worked. However, I do have concerns about the "Oh, we'll just > lash together a binding to C" attitude common among lua programmers; I > foresee maintainability problems and the possibility of slow death by > low-level details as that strategy tries to scale up.
I think this is quite a prediction? Could you give an example scenario? How would another language (e.g. Python) mitigate this?
> And, of course, one problem with calling back into C a lot is that > you walk back into C's resource-management issues.
C resource management can be effectively dealt with by relying on Lua's GC to track C resources via userdata.
> My sense is that git's use cases are better served by a glue language > in the Python/Perl/Ruby class rather than an extension langage. But > my mind is open on this issue.
I don't see how these languages are more appropriate based on your concerns.
-- - Patrick Donnelly