From: "Daniel C." <bigatojj@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] removing python
Date: Mon, 14 Jun 2021 17:06:45 -0300 [thread overview]
Message-ID: <823c3ace-e56f-675b-7ec3-10a8b7a14ac2@gmail.com> (raw)
In-Reply-To: <BF01F33CB69E812F3D3AB38A13DD2768@eigenstate.org>
Em 14/06/2021 13:34, ori@eigenstate.org escreveu:
> It was on the order of a million lines of
> code. The python version was from 2007,
> and the hg version was from 2009.
> [...]
> Contrast: Our implementation of git is 8784
> lines of code (at the moment), and doesn't
> have any external dependencies that we need
> to fight.
>
Wow, the contrast is astonishing, congratulations and thank you for your
work. That sounds like a major milestone.
The size of the git implementation seems so small (maybe misleadingly
so?) that it makes me curious, because it's been a while since I first
heard that you were working on git9. Why did it took so long, was it
merely because you didn't have much free time? Or was it hard to
understand git? Sometimes when migrating something, I see that I spend
more time understanding the old system than writing the new one. Was
that the case? What was the harder aspects in this implementation?
Because a superficial look would suggest that with the new
implementation being so short, it should not have taken so long. I'm
sure it would be naive to think this way. Knowing that often making
something simple and clear takes a lot more effort than producing
something complicated, I would be grateful for any insight you want to
share on the history behind the scenes for this transition. Thanks!
next prev parent reply other threads:[~2021-06-14 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 0:09 ori
2021-06-14 0:19 ` Stephen M. Jones
2021-06-14 1:16 ` Stanley Lieber
2021-06-14 1:52 ` ori
2021-06-14 2:37 ` Stanley Lieber
2021-06-14 15:16 ` Alexander McLin
2021-06-14 16:25 ` Alex Musolino
2021-06-14 16:34 ` ori
2021-06-14 20:06 ` Daniel C. [this message]
2021-06-14 20:34 ` ori
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=823c3ace-e56f-675b-7ec3-10a8b7a14ac2@gmail.com \
--to=bigatojj@gmail.com \
--cc=9front@9front.org \
/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).