9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] bio io functions
Date: Fri, 5 May 2017 07:05:19 -0400	[thread overview]
Message-ID: <75A8C359-FA78-4E6E-AD9C-559383913866@stanleylieber.com> (raw)
In-Reply-To: <CAJQxxw=a=zxbThgNqRi8o+iidq+AfdhabBw4sRNjxoEg6wb=tg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]

On May 5, 2017, at 6:33 AM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
> 
> Just stating what I've learnt.
> 
> brucee
> 
>> On 5 May 2017 at 20:32, Stanley Lieber <sl@stanleylieber.com> wrote:
>>> On May 5, 2017, at 6:29 AM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
>>> 
>>> Go programs run fine on plan9. There are many benefits in replacing plan9 programs with a Go equivalent, e.g. the widespread deployment of algorithms that use parallelism. What a faster cleaner world it would be.
>>> 
>>> brucee
>>> 
>>>> On 5 May 2017 at 20:21, Stanley Lieber <sl@stanleylieber.com> wrote:
>>>> 
>>>> 
>>>>> On May 5, 2017, at 5:14 AM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
>>>>> 
>>>>> I don't use primitive methods - like bubblesort. I'm saying Go does it better and elegantly.
>>>>> 
>>>>> brucee
>>>>> 
>>>>>> On 5 May 2017 at 19:11, hiro <23hiro@gmail.com> wrote:
>>>>>> On 5/4/17, Bruce Ellis <bruce.ellis@gmail.com> wrote:
>>>>>> > Go provides this functionality using interfaces.
>>>>>> 
>>>>>> are you saying this solution is unnecessarily primitive because it
>>>>>> doesn't use the high level abstraction if interfacing?
>>>> 
>>>> Plan 9 has not yet been re-implemented in Go.
>>>> 
>>>> sl
>> 
>> Okay, but is this a pull request or are you just volunteering our Germans for your space program?
>> 
>> sl

Not trying to be a dick, just observing that a C library function used throughout the system might not be the first place to start sneaking in Go. The implication would obviously be rewriting all the programs that rely upon it in this other language, and that would be a big job. "Just use Go" in this context is either unrealistic advice or a non sequitur.

Other nits: Go is not really a first class citizen on Plan 9. It cannot even be bootstrapped on 9front/386 or 9front/arm. There are unfixed bugs that complicate networking and process reclamation. For these and other reasons, the Germans already declared 9front would never ship Go. Circling back to the original suggestion, this precludes rewriting the system in Go.

Go offers some advantages over C, but also brings with it a lot of code, mechanism, and culture that attempts to solve problems that are not even present in Plan 9. I run Go programs on production Plan 9 systems every day, but it's not quite so simple as just re-implementing stuff that already works in a completely different language just to... What, exactly?

sl


[-- Attachment #2: Type: text/html, Size: 4280 bytes --]

  reply	other threads:[~2017-05-05 11:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 16:02 Julius Schmidt
2017-05-04 16:23 ` [9front] " Benjamin Purcell
2017-05-04 17:52   ` Giacomo Tesio
2017-05-04 20:18     ` Bruce Ellis
2017-05-04 20:21       ` Benjamin Purcell
2017-05-05  9:11       ` hiro
2017-05-05  9:14         ` Bruce Ellis
2017-05-05  9:55           ` Julius Schmidt
2017-05-05  9:56             ` Bruce Ellis
2017-05-05 10:21           ` Stanley Lieber
2017-05-05 10:29             ` Bruce Ellis
2017-05-05 10:32               ` Stanley Lieber
2017-05-05 10:33                 ` Bruce Ellis
2017-05-05 11:05                   ` Stanley Lieber [this message]
2017-05-05 12:11                   ` hiro
2017-05-05 15:24               ` Kurt H Maier

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=75A8C359-FA78-4E6E-AD9C-559383913866@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    /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).