9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchovski@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [GSOC 2013] Implement plan9 commands in Go, Goblin
Date: Mon, 29 Apr 2013 14:22:20 -0600	[thread overview]
Message-ID: <CAK4xykXOcTaic35V0yC32PK_acxia=_hpCW5J9G89OsaS_zWvw@mail.gmail.com> (raw)
In-Reply-To: <0ce81c0d523e2d6b9e56042460ec61d6@coraid.com>

> do you envision a system with no shell at all?

I haven't thought about a system, but as I was going through a similar
exercise I decided that instead of copying the code I would put on my
go hat on and implement from scratch with whatever tools go gave me.
Freq for example uses the standard hashmap. Cmp, comm and uniq spawn
readers that concurrently gobble up the inputs while a state machine
implements the logic via select{} on channels. I can see those willing
to build a system out of this leveraging go's fast compilation and
distribute only a shell and compiler+linker, but I can't speak for
them.

Of course, the benefits of such a rewrite for the sake of
"re-imagination" are only marginal in most cases because the Plan 9
programs are very well thought-out high quality code. I just don't
want to see it blindly rewritten without any thought put into it. Or,
rather, don't want to do it myself :)



  reply	other threads:[~2013-04-29 20:22 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-29 18:47 Alex-P. Natsios
2013-04-29 18:53 ` Alex-P. Natsios
2013-04-29 18:59   ` erik quanstrom
2013-04-29 19:11     ` Aram Hăvărneanu
2013-04-29 19:17       ` erik quanstrom
2013-04-29 19:27       ` arnold
2013-04-29 19:31         ` Aram Hăvărneanu
2013-04-29 19:33           ` Aram Hăvărneanu
2013-04-30  5:42       ` Jens Staal
2013-04-30  8:11         ` Bence Fábián
2013-04-30  9:00           ` Alex-P. Natsios
2013-04-30 15:26           ` Aram Hăvărneanu
2013-04-30 15:31             ` erik quanstrom
2013-04-30 15:41               ` Kurt H Maier
2013-04-30 15:44             ` Bence Fábián
2013-04-30 15:46             ` tlaronde
2013-04-30 18:18               ` Steve Simon
2013-04-30 21:03                 ` Steve Simon
2013-04-30 22:23                   ` suharik
2013-04-30 22:25                     ` erik quanstrom
2013-04-30 22:50                       ` suharik
2013-04-30 22:54                         ` erik quanstrom
2013-04-30 23:44                           ` suharik
2013-04-30 23:50                             ` Brantley Coile
2013-05-01  0:56                             ` erik quanstrom
2013-05-01  5:05                               ` Matthew Veety
2013-05-03 13:31                   ` Yaroslav
2013-04-30 21:03                 ` Paul Patience
2013-05-01  6:49                 ` tlaronde
2013-04-30 12:28         ` erik quanstrom
2013-04-29 19:00   ` Aram Hăvărneanu
2013-04-29 19:52     ` andrey mirtchovski
2013-04-29 19:58       ` erik quanstrom
2013-04-29 20:22         ` andrey mirtchovski [this message]
2013-04-29 20:00       ` Aram Hăvărneanu
2013-04-29 20:02         ` erik quanstrom
2013-04-29 22:45       ` Kurt H Maier
2013-04-29 21:59         ` andrey mirtchovski
2013-05-01  9:30 ` mortdeus
2013-05-01 10:58 ` mortdeus
2013-05-01 11:13   ` Alex-P. Natsios
2013-05-01 13:38 ` mortdeus
2013-05-02  0:02 ` erik quanstrom
2013-05-02  0:11   ` andrey mirtchovski
2013-05-02  1:01     ` Devon H. O'Dell
2013-05-02  1:06       ` erik quanstrom
2013-05-02  1:57     ` Lyndon Nerenberg
2013-05-02  3:34     ` Matthew Veety

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='CAK4xykXOcTaic35V0yC32PK_acxia=_hpCW5J9G89OsaS_zWvw@mail.gmail.com' \
    --to=mirtchovski@gmail.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).