9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Roman Shaposhnik <roman@shaposhnik.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go
Date: Tue, 10 Nov 2009 23:25:54 -0800	[thread overview]
Message-ID: <e763acc10911102325i26d27676o11f69f2f41224cf0@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0911102200g556345a5p946974f7b7c10dd3@mail.gmail.com>

On Tue, Nov 10, 2009 at 10:00 PM, Russ Cox <rsc@swtch.com> wrote:
> 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.

First of all -- as usual -- thanks a million for chiming in. Two question:
    1. what would be the best way to quickly wrap one's head around Go?
    2. Is there an alias dedicated to "Go for Plan9/Inferno/Limbo old geezers"?
        I'm pretty sure such a perspective could be a little odd for most of
        of the folks on go-nuts, but at the same time this is a perspective I'm
        personally coming from (and it looks like I'm not alone).

Thanks,
Roman.

P.S. Its just not fair to have "Go for C++ programmers" ;-)



  parent reply	other threads:[~2009-11-11  7:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11  6:00 Russ Cox
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 [this message]
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=e763acc10911102325i26d27676o11f69f2f41224cf0@mail.gmail.com \
    --to=roman@shaposhnik.org \
    --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).