From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Go for systems programming
Date: Fri, 17 May 2013 12:49:37 -0400 [thread overview]
Message-ID: <0efa6720b22c45b0ee9ab7cdb10c5968@coraid.com> (raw)
In-Reply-To: <03BB70B9-8ED4-4A39-B19E-2B0481DEBC13@gmail.com>
> In its own niche is the important point here. Just because writing a
> kernel or system utilities can be done in Go doesn't mean it should
> be. Go isn't even totally stable or feature complete on Plan 9 at
> this point. You get the same shit in C on Plan 9 as you do Go plus
> it's more stable and has better support. At this point I would say
> keep using C unless you have some specific need to use Go on Plan 9.
if you rewrote a kernel in go, i don't think you'd want something that
is exactly plan 9.
- erik
next prev parent reply other threads:[~2013-05-17 16:49 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
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 [this message]
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=0efa6720b22c45b0ee9ab7cdb10c5968@coraid.com \
--to=quanstro@labs.coraid.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).