From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii From: Steve Simon Mime-Version: 1.0 (1.0) Date: Tue, 24 Sep 2019 10:53:29 +0100 Message-Id: <47D55257-12D0-4ABB-BD6E-2A9FF7484C4F@quintile.net> References: <8fe7f4f0-f6bc-2ba1-468f-517d27817259@gmail.com> <8325b375-3363-8d16-4ff0-1f8426c61f19@gmail.com> In-Reply-To: <8325b375-3363-8d16-4ff0-1f8426c61f19@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] building Alef language Topicbox-Message-UUID: 781b2f8e-ec36-11e9-914b-36aef4b1d025 You need a license to run the 1st and 2nd ed. The 2nd ed books/cds (and thus the license) have not been printed for a long= time. the images may have leaked but i think we should still try to respect the te= rms of the license. -Steve > On 23 Sep 2019, at 2:01 am, Sean Hinchee wrote: >=20 > You could also just run 2e in a VM and show it off there :) >=20 > 2e can be coaxed into running under virtualbox, even. >=20 > Cheers, > Sean >=20 >> On 9/22/19 12:46 AM, Phil Kulin wrote: >> 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 wrote= : >>>=20 >>> I have a version for legacy Plan 9, lightly tested, that I have not >>> looked at in ages. >>>=20 >>> 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. >>>=20 >>> Don't forget the rationale for dropping Alef: support for the >>> language, across many architectures and including many libraries would >>> have been crippling. >>>=20 >>> Both of those are now Go's strong suits. >>>=20 >>> Lucio. >>>=20 >>> PS: A tar archive may be on sources under "proxima" - it's been a long t= ime. >>>=20