From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go for systems programming
Date: Fri, 17 May 2013 11:45:06 -0700 [thread overview]
Message-ID: <62419D19-446D-4D83-96A6-17895A0B39FD@bitblocks.com> (raw)
In-Reply-To: <160BE4B6-B0A1-47FC-9F5C-C26021164CE4@gmail.com>
On May 17, 2013, at 9:07 AM, Nemo <nemo.mbox@gmail.com> wrote:
> If you remove the features that make go interesting you'd get C without
> punctuation symbols.
Agreed.
I don't see what's the big deal about doing GC In an OS kernel. And the features that make Go interesting can be useful at the kernel level too.
On the other hand, may be the kernel can be made much more minimal and where most everything is done by user level services. But as Erik says it wouldn't be plan9. In Go it might be more natural to have a syschannel instead of syscalls (actual syscalls might end up being just send and receive).
On the other other hand, to really dethrone C, there needs to be a Go compiler in Go and an OS in Go! We know both can be done but actually doing so can throw up a bunch of surprises.
next prev parent reply other threads:[~2013-05-17 18:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 15:51 lamg
2013-05-17 16:07 ` Nemo
2013-05-17 18:45 ` Bakul Shah [this message]
2013-05-17 19:23 ` hiro
2013-05-17 20:31 ` Kurt H Maier
2013-05-17 20:37 ` erik quanstrom
2013-05-17 20:42 ` Bakul Shah
2013-05-17 20:46 ` Matthew Veety
2013-05-17 21:05 ` Bakul Shah
2013-05-17 21:53 ` Kurt H Maier
2013-05-18 3:17 ` erik quanstrom
2013-05-17 16:31 ` Matthew Veety
2013-05-17 16:49 ` erik quanstrom
2013-05-17 17:28 ` Skip Tavakkolian
2013-05-17 17:53 ` lamg
2013-05-17 20:29 ` Charles Forsyth
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=62419D19-446D-4D83-96A6-17895A0B39FD@bitblocks.com \
--to=bakul@bitblocks.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).