9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] removing python
Date: Mon, 14 Jun 2021 16:34:14 -0400	[thread overview]
Message-ID: <D44EF5A1D4A0F574E100AABA194B5418@eigenstate.org> (raw)
In-Reply-To: <823c3ace-e56f-675b-7ec3-10a8b7a14ac2@gmail.com>

Quoth Daniel C. <bigatojj@gmail.com>:
> 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?

It's been usable enough to host its own development for
almost two years (the first import from hg was Jun 28 2019,
and every commit since the conversion has been done with
git9, for the sake of dogfooding and bragging rights).

But it takes experience with the program to find the rough
edges, poor design decisions, and bugs. And hg was working
well enough, so there was no pressure to rush a conversion,
and good reason to do it when things felt smooth, and all
the features and ui that we cared about felt reasonably
polished.

And, yes, it takes time for me to think about how to write
simple and clean implementations of algorithms without a
ton of special cases.


      reply	other threads:[~2021-06-14 20:43 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.
2021-06-14 20:34             ` ori [this message]

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=D44EF5A1D4A0F574E100AABA194B5418@eigenstate.org \
    --to=ori@eigenstate.org \
    --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).