From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] building Alef language
Date: Tue, 24 Sep 2019 10:53:29 +0100 [thread overview]
Message-ID: <47D55257-12D0-4ABB-BD6E-2A9FF7484C4F@quintile.net> (raw)
In-Reply-To: <8325b375-3363-8d16-4ff0-1f8426c61f19@gmail.com>
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 terms of the license.
-Steve
> On 23 Sep 2019, at 2:01 am, Sean Hinchee <henesy.dev@gmail.com> wrote:
>
> You could also just run 2e in a VM and show it off there :)
>
> 2e can be coaxed into running under virtualbox, even.
>
> Cheers,
> Sean
>
>> 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 <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.
>>>
next prev parent reply other threads:[~2019-09-24 9:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 20:45 Phil Kulin
2019-09-20 21:05 ` Rodrigo G. López
2019-09-21 2:40 ` Sean Hinchee
2019-09-21 3:14 ` Lucio De Re
2019-09-21 12:33 ` hiro
2019-09-22 7:46 ` Phil Kulin
2019-09-22 9:38 ` Rodrigo G. López
2019-09-22 9:44 ` Ethan Gardener
2019-09-23 1:01 ` Sean Hinchee
2019-09-24 9:53 ` Steve Simon [this message]
2019-09-24 11:25 ` hiro
2019-09-24 11:56 ` Rodrigo G. López
2019-09-25 6:40 ` Sergey Zhilkin
2019-09-25 17:35 ` Steve Simon
2019-10-08 15:06 ` Sergey Zhilkin
2019-10-08 19:50 ` Phil Kulin
2019-10-08 20:24 ` Sergey Zhilkin
2019-10-08 21:54 ` Steve Simon
2019-09-21 14:05 ` Phil Kulin
2019-09-21 17:58 ` Phil Kulin
2019-09-21 20:45 ` Phil Kulin
2019-09-21 23:00 ` Rodrigo G. López
2019-09-22 7:08 ` Phil Kulin
2019-09-22 9:27 ` Ethan Gardener
2019-09-22 9:33 ` Phil Kulin
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=47D55257-12D0-4ABB-BD6E-2A9FF7484C4F@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).