all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Caleb Ristvedt <caleb.ristvedt@cune.org>
Cc: guix-devel@gnu.org
Subject: Re: GSoC final update
Date: Tue, 29 Aug 2017 10:32:15 +0200	[thread overview]
Message-ID: <87r2vukc4w.fsf@igalia.com> (raw)
In-Reply-To: <87lgm224xz.fsf@cune.org> (Caleb Ristvedt's message of "Tue, 29 Aug 2017 02:44:56 -0500")

On Tue 29 Aug 2017 09:44, Caleb Ristvedt <caleb.ristvedt@cune.org> writes:

> <Digression> I found myself checking the guile reference quite
> frequently. One time I happened upon a part describing the ECMAScript
> implementation (curiosity and all that), and noticed that several times
> it was mentioned how irresponsible the implementor was. That scared me
> probably more than it should have. By all objective criteria, I have
> failed in this project, and it frightens me to think that, nice as the
> community is, I could screw up badly enough to end up a footnote
> somewhere as an example of what not to be. That fear pretty much sums up
> my mental state during the second half of the summer.</Digression>

LOL I wrote that about myself :-) As in, the ECMAScript implementation
was mostly mine, and its faults were mine, and I documented that and
moved on.  It would be nice to fix some day but it takes time; in the
meantime I just wanted to moderate peoples' expectations.  Apologies if
that language made you feel intimidated, the intention was precisely the
opposite.

Happy hacking! :-)

Andy

  reply	other threads:[~2017-08-29  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29  7:44 GSoC final update Caleb Ristvedt
2017-08-29  8:32 ` Andy Wingo [this message]
2017-08-29 10:59 ` Efraim Flashner
2017-08-29 22:52 ` Leo Famulari
2017-08-30  9:50 ` Ludovic Courtès
2017-08-30 12:03 ` Ricardo Wurmus
2017-08-30 16:04 ` Andreas Enge
2017-08-31 14:49   ` Ludovic Courtès

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=87r2vukc4w.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=caleb.ristvedt@cune.org \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.