On Mon, Oct 23, 2023 at 12:01:14PM -0700, Junio C Hamano wrote:
> Ah, OK, now I see where your "--table" is coming from ;-).
> "git-sim" was exactly what I thought about when I saw it, and I did
> not know that "--table" came from the same set of brain cells.
Haha the set is not quite the same I'm sure I've lost many over the
course of this year. But the survivors are doing their best.
> One thing that nobody seems to have raised that disturbs me is that
> even though there may be educational value in having such a
> "feature", having to carry the extra code to implement in Git incurs
> extra cost. I was reasonably happy when I saw that "git-sim" was
> done as a totally separate entity exactly for this reason.
Erm, not to get too sappy here but I'd love to maintain anything related
to this that gets implemented, in whatever form that turns out to be.
I already spend way too much of my free time working on Git-related
things so making this contribution to Git itself would mean a lot to me.
Starting Git-Sim as a separate entity made sense to me because:
* I had no idea whether anyone wanted something like this, so it
would have made for a pretty weak argument to the community. (It
turned out way more users were interested than I thought).
* It's written in Python and relies on a dependency library called
Manim, so I thought it wouldn't make any sense to try and wedge
that into the Git codebase.
* The output is presentation quality images / video animations, which
is unlike anything I've seen outputted by any Git command. (I didn't
explore what it would take to do something similar in C).
The main downsides to Git-Sim as a separate tool are:
* The main downside is lack of reach. Not being Git-native means only
a tiny fraction of Git users will ever know it exists.
* There is technically no guarantee that a simulated output actually
corresponds to what the command will do, as highlighted by this
comment on Hacker News: "Next HN post - "I destroyed my repo - but
it WORKED in Git-Sim!"
* As Git changes over time, Git-Sim is destined to be a step behind.
* Certain commands (like the networked commands fetch/push/pull/etc)
are not easy to simulate without doing horrible things like cloning
a new copy of the repo behind the scenes, running the desired
operation on it, and checking the result. I assume things like this
would be a lot easier to do within Git.
