9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go
Date: Tue, 10 Nov 2009 22:00:43 -0800	[thread overview]
Message-ID: <dd6fe68a0911102200g556345a5p946974f7b7c10dd3@mail.gmail.com> (raw)

On Tue, Nov 10, 2009 at 4:54 PM, Joseph Stewart
<joseph.stewart@gmail.com> wrote:
> Hmmm... is this Limbo/Newsqueak/Alef inspired?  http://golang.org

Sure.

On Tue, Nov 10, 2009 at 5:00 PM, andrey mirtchovski
<mirtchovski@gmail.com> wrote:
> but will it run on Plan 9?

Not yet.  It shouldn't be much effort to port if someone is
interested, but it isn't a matter of just typing mk either.
The main hurdle for the 386 tools is that Go assumes it can
set up a local segment descriptor for a kind of thread-local
storage.  The Plan 9-friendly approach is probably to use a
fixed high stack address for the local storage instead.
Then you'd have to write the OS stuff too.  I need to write a
how-to about porting to a new system.

On Tue, Nov 10, 2009 at 5:04 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> On Tue Nov 10 20:02:34 EST 2009, mirtchovski@gmail.com wrote:
>> but will it run on Plan 9?
>
> would the authors care to contrast go with limbo?

The common concepts—channels, slices, and cheap processes—
have their differences: channels can be typed as one direction or
another, slices have a cap, the processes can be muxed onto
multiple OS threads instead of limited to a single OS thread.
The new concepts are new and shouldn't be ignored: interface types,
the approach to constants, the package system, initialization,
methods on almost any type, the very simple approach to name
visibility (case-sensitive instead of public/private tags), and
other things I am forgetting all combine to make Go feel like
a very different language than Limbo, or for that matter Alef or
Newsqueak.  Don't fall into the trap of thinking it's just like one
of those.

Another contrast with Limbo is that the language compiles to
machine code instead of byte codes.

On Tue, Nov 10, 2009 at 5:15 PM, Roman Shaposhnik <roman@shaposhnik.org> wrote:
> P.S. Russ, are you working for Google now?

Yes.

On Tue, Nov 10, 2009 at 5:27 PM, andrey mirtchovski
<mirtchovski@gmail.com> wrote:
> serious question: can i have a link to the 9p implementation, pretty
> please? it doesn't appear in the module list on their website.

There's no 9p implementation.  I thought about writing one
a couple times, and I'd love to do that (I want to write acme
extensions in Go), but it hasn't been a priority.  Another thorny
issue is what to name the package, since you can't start a
package name with a digit.

On Tue, Nov 10, 2009 at 7:56 PM, hiro <23hiro@googlemail.com> wrote:
> have you also seen this vid?
> http://www.youtube.com/watch?v=rKnDgT73v8s

Yes.

Russ


             reply	other threads:[~2009-11-11  6:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11  6:00 Russ Cox [this message]
2009-11-11  6:33 ` Anant Narayanan
2009-11-11  6:47 ` Skip Tavakkolian
2009-11-11 11:27   ` Eris Discordia
     [not found]   ` <D67AC32CFE1076880E2CDDD5@192.168.1.2>
2009-11-11 16:25     ` John Waters
2009-11-11 17:23       ` roger peppe
2009-11-11  7:25 ` Roman Shaposhnik
2009-11-11 17:23   ` Russ Cox
2009-11-12  5:08     ` andrey mirtchovski
2009-11-12  5:25       ` Russ Cox
2009-11-12  5:46         ` Jeff Sickel
2009-11-12  6:39           ` Russ Cox
2009-11-12 16:37             ` Michaelian Ennis
2009-11-12 17:09 ` AngryDude
2009-11-12  4:31 Nick LaForge
2009-11-12  5:27 ` Roman Shaposhnik
2009-11-12 15:28   ` Devon H. O'Dell
2009-11-12 20:51   ` Nick LaForge
     [not found] <<9ab217670911120728q137ac2c1j4f11d9a1d8b2ded5@mail.gmail.com>
2009-11-12 16:37 ` erik quanstrom
2009-11-12 16:59   ` Devon H. O'Dell
2009-11-12 18:49   ` Roman Shaposhnik
     [not found] <<9ab217670911120859u25b8f6f0m57cad5c126d75d65@mail.gmail.com>
2009-11-12 17:13 ` erik quanstrom
2009-11-12 17:29   ` LiteStar numnums
2009-11-12 18:40   ` Tharaneedharan Vilwanathan

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=dd6fe68a0911102200g556345a5p946974f7b7c10dd3@mail.gmail.com \
    --to=rsc@swtch.com \
    --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).