From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
References: <CAK=u2EV-0bU82kq3RiTARJwWjXJsi4HyDq9seen3ETmQdAp_Fg@mail.gmail.com>
	<CA+cCjXr2nQv1qghErctdmn5pEMOK5eyUZ4ZNd6tBPgBe+rV+Kw@mail.gmail.com>
	<8fe7f4f0-f6bc-2ba1-468f-517d27817259@gmail.com>
	<CAJQ9t7gZHS_0gED3Luu9dJYuvCkhgr-+gpfPGf0BkixgU9T5Vg@mail.gmail.com>
In-Reply-To: <CAJQ9t7gZHS_0gED3Luu9dJYuvCkhgr-+gpfPGf0BkixgU9T5Vg@mail.gmail.com>
From: Phil Kulin <schors@gmail.com>
Date: Sun, 22 Sep 2019 10:46:25 +0300
Message-ID: <CAK=u2EW=Nh3PJ=p6W1t8gCXQY1FVFoTPyujGkjAXe8gAvNg6Pg@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [9fans] building Alef language
Topicbox-Message-UUID: 0a8b8bc4-eada-11e9-9d60-3106f5b1d025

You right. I am preparing slides for my report on upcoming
GolangConf-2019 in Moscow. I need Alef, libthread and Limbo for
explaining some golang features.

On Sat, Sep 21, 2019 at 6:16 AM Lucio De Re <lucio.dere@gmail.com> wrote:
>
> I have a version for legacy Plan 9, lightly tested, that I have not
> looked at in ages.
>
> Happy to haul it out, but I see little value in it. Go may have
> idiosyncrasies, but it is much more suited to modern architectures.
> That said, had Go not surfaced, I would have much preferred Alef to
> many other options.
>
> Don't forget the rationale for dropping Alef: support for the
> language, across many architectures and including many libraries would
> have been crippling.
>
> Both of those are now Go's strong suits.
>
> Lucio.
>
> PS: A tar archive may be on sources under "proxima" - it's been a long time.
>


-- 
Non nobis Domine non nobis sed Nomini Tuo da gloriam
Phil Kulin