Notes from the Git Contributor's Summit, 2023

Interesting comments on librarification:

    * (Emily) If we had the capacity to write portions of Git's code in Rust (memory
    safety, performance, use it as a library), would we want to use it?
    * (Junio) I notice in the participant list people like Randall who work on
        NonStop. I'd worry about the effect on minority stakeholders, portability.
    * (Junio) Not fundamentally opposed to the direction.
    * (Elijah) did not parallelize the C implementation of the new ORT backend.
    Wanted to rewrite it in Rust, cleaned up headers as a side-effect, and looked
    at other bits. Merge backends are already pluggable, could have a "normal" one
    in addition to a Rust backend.
    * (Emily) If we already have something in C that establishes an existing API
    boundary, that makes it more tenable to rewrite it in Rust. Could say that the
    C version is deprecated and make future changes to Rust.

If Git manages to split out parts of the codebase into a few core libraries, that would definitely be interesting to a lot of people who are (still) using libgit2 today. GitLab and Github say they both finished migrating away and completely stopped using libgit2, but I think a lot more people would benefit from an official library, beyond just the big forges.

Especially people on Windows, where starting a lot of short-lived CLI processes is noticeably expensive