9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Chris McGee <newton688@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Is Plan 9 C "Less Dangerous?"
Date: Mon,  3 Sep 2018 08:40:28 -0400	[thread overview]
Message-ID: <F102EB67-833D-4E79-BECB-DE6B1692963C@gmail.com> (raw)
In-Reply-To: <CAJQ9t7gNAywpPgfb1ywaxhBwCZU+VgaZRLp1F1tTGzyWL3o7aA@mail.gmail.com>

Thanks everyone. This is pretty much what I expected was the case. I just wanted to confirm my understanding.

Plan 9 C was re-engineered with some
focus on readable code. Readability is expected to make bugs more apparent, making it less “dangerous.” Linux is so huge and hard to read that even simple things like C have become sharp edges that cut people. While the idea that many eyes makes bugs shallower seems to have failed in the world of complex behemoth software it may work here.

I’ve read some of the 9front kernel code trying to make it work on raspberry pi. I admit that I didn’t find any bugs at that time. The code is relatively easy to follow even for me. So, I suppose it’s working nicely.

Chris

> On Sep 3, 2018, at 12:07 AM, Lucio De Re <lucio.dere@gmail.com> wrote:
> 
>> On 9/2/18, hiro <23hiro@gmail.com> wrote:
>> "prevailing wisdom" sounds like an oxymoron.
>> 
> Yes, real wisdom is for some (evolutionary? counter-evolutionary?)
> reason unlikely to prevail.
> 
> Go figure.
> 
> Lucio.
> 



  reply	other threads:[~2018-09-03 12:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 16:31 Chris McGee
2018-09-02 16:52 ` hiro
2018-09-03  4:07   ` Lucio De Re
2018-09-03 12:40     ` Chris McGee [this message]
2018-09-03 17:58       ` Ethan Gardener
2018-09-04 10:51         ` Lucio De Re
2018-09-04 11:33           ` Ethan Gardener
2018-09-04 11:41             ` Chris McGee
2018-09-02 18:16 ` Lucio De Re
2018-09-02 19:18   ` Steve Simon
2018-09-02 19:21 ` Iruatã Souza
2018-09-03  1:03   ` Charles Forsyth
2018-09-03  2:03 ` Skip Tavakkolian
2018-09-04 23:17 ` Charles Forsyth
2018-09-04 23:30   ` Tyga
2018-09-05  2:29     ` Chris McGee
2018-09-05 11:23       ` Dave MacFarlane
2018-09-05 11:42         ` Chris McGee
2018-09-05 13:35           ` Ethan Gardener
2018-09-05 15:38           ` Iruatã Souza
2018-09-05 23:59             ` Chris McGee
2018-09-06  0:32           ` Bakul Shah
2018-09-06  3:40             ` Lucio De Re
2018-09-06 11:41               ` Chris McGee
2018-09-06 13:37             ` Ethan Gardener
2018-09-06 17:48           ` Richard Miller
2018-09-06 19:08             ` Skip Tavakkolian
2018-09-06 21:21             ` Chris McGee
2018-09-07  8:32               ` Richard Miller
2018-09-05  3:25     ` Ori Bernstein
2018-09-05  8:19       ` Ethan Gardener

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=F102EB67-833D-4E79-BECB-DE6B1692963C@gmail.com \
    --to=newton688@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).