From: athiele@charter.net
To: 9fans@cse.psu.edu
Subject: Re: Squeak -- Re: [9fans] uncompressing .tar.Z
Date: Mon, 11 Nov 2002 08:51:41 -0500 [thread overview]
Message-ID: <c8e73b5d1a45c7bf84e31e499f3a9175@charter.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 349 bytes --]
Yes Smalltalk Squeak.
It just seems like a good fit. I downloaded the sources today to see how far off we are. It really doesn`t look that bad. Currently, I don`t have the time for an all out port effort, but I will see what I can do.
Please keep me updated if the Hangar 18 crew does any work, that way we can coordinate efforts.
Adrian
[-- Attachment #2: Type: message/rfc822, Size: 2317 bytes --]
From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Cc: <hangar18-general@open-forge.org>
Subject: Squeak -- Re: [9fans] uncompressing .tar.Z
Date: Mon, 11 Nov 2002 07:32:56 -0600 (CST)
Message-ID: <Pine.LNX.4.33.0211110730540.2217-100000@einstein.ssz.com>
On Sun, 10 Nov 2002 athiele@charter.net wrote:
> What do you think about the Squeak thing ?
Is that Squeak as in Smalltalk Squeak? Very cool.
A couple of us in Hangar 18 are using it. There is
apparently some connection with Austin, Tx. since
they make specific mention of it in the book. One
of my goals for next year is to talk to them about
a port to Plan 9.
--
____________________________________________________________________
We don't see things as they are, ravage@ssz.com
we see them as we are. www.ssz.com
jchoate@open-forge.org
Anais Nin www.open-forge.org
--------------------------------------------------------------------
next reply other threads:[~2002-11-11 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 13:51 athiele [this message]
2002-11-11 22:27 ` Jim Choate
-- strict thread matches above, loose matches on Subject: below --
2002-11-11 16:58 Russ Cox
2002-11-11 17:12 ` Dan Cross
2002-11-11 23:07 ` Jim Choate
2002-11-10 23:24 athiele
2002-11-11 13:32 ` Squeak -- " Jim Choate
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=c8e73b5d1a45c7bf84e31e499f3a9175@charter.net \
--to=athiele@charter.net \
--cc=9fans@cse.psu.edu \
/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).