From: Roman Shaposhnik <roman@shaposhnik.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go
Date: Thu, 12 Nov 2009 10:49:00 -0800 [thread overview]
Message-ID: <e763acc10911121049r90e941i754e25156b47c488@mail.gmail.com> (raw)
In-Reply-To: <fb755944c9e58c38155041180dffa483@ladd.quanstro.net>
On Thu, Nov 12, 2009 at 8:37 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> > Speaking of VMs (and Limbo) -- I'm wondering if Go is eventually going
>> > to have it anyway. Any reason not to?
>>
>> It can be perceived as a competitor to C if it has a runtime, but not
>> if it has a VM. So I don't think it would grow one.
>
> why do you think the goal is to be
> perceived as a competitor to c?
Good question. In fact, I'd say any language that has a non-trivial
runtime library is not actually competing with C. C is a portable assembler
and that's why I, personally, like it so much -- its runtime is pure hardware
(both physical and virtual).
To some extent -- that's the reason I'm asking my VM question. I think any
non-trivial runtime is VM envy. Besides with JIT like capabilities you can
actually run faster in a VM setting.
> one thing that's not clear to me from
> the faq (perhaps it's clarified in robs talk?)
> and i haven't worked out for myself yet, is if
> one could write operating system code in
> go. and if so, what would the language
> restrictions be.
If what you mean is "writing a kernel" then my take so far
is -- garbage collection and concurrency support might get
in the way. However, as always, I'd be very curious to find out
Russ' take on it.
Thanks,
Roman.
next prev parent reply other threads:[~2009-11-12 18:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[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
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
-- strict thread matches above, loose matches on Subject: below --
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
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
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=e763acc10911121049r90e941i754e25156b47c488@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).