9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Gardener <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] Is Plan 9 C "Less Dangerous?"
Date: Wed,  5 Sep 2018 09:19:21 +0100	[thread overview]
Message-ID: <1536135561.3026040.1497260856.5FF478D2@webmail.messagingengine.com> (raw)
In-Reply-To: <20180904202500.d4e629511996125d643d7635@eigenstate.org>

On Wed, Sep 5, 2018, at 4:25 AM, Ori Bernstein wrote:
>
> > CPUs, such as Intel/AMD x64
> > are vastly more complex so "optimising" C compilers are trying to make
> > something simple take advantage of something far more complex.
>
> Ironically, because of the complexity in the CPUs, many of the optimizations
> make less of a difference now -- they're essentially optimizing just in time
> compilers under the hood, so even terrible code will run acceptably quickly.

This is an example of a real benefit to complexity, one I'm personally happy about.  It's good for us 9fans, whether we want to use Plan 9's 20 year old compilers, or implement our own compilers for new or existing languages, or whatever.

My ego still tries to complain about using something I don't understand, but in doing so it's really fighting its own interests.

--
The lyf so short, the craft so long to lerne. -- Chaucer



      reply	other threads:[~2018-09-05  8:19 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
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 [this message]

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=1536135561.3026040.1497260856.5FF478D2@webmail.messagingengine.com \
    --to=eekee57@fastmail.fm \
    --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).