The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: David Arnold <davida@pobox.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
	Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [TUHS] Who's behind the UNIX filesystem permission
Date: Fri, 2 Aug 2019 14:36:47 +1000	[thread overview]
Message-ID: <CAKzdPgxNjCEdEOu4b06AKLfzLB0GLphu71M8g=XFRpjRSz7yhw@mail.gmail.com> (raw)
In-Reply-To: <A7F61221-47D0-4A21-82FC-F0201F085990@pobox.com>

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

In Go we "just" dedicate a core to GC, problem solved. The arrival of
universal multi-CPU hardware made than option. Some tremendous technical
work required (for which I take zero credit; see
https://blog.golang.org/ismmkeynote) but yeah.

-rob


On Fri, Aug 2, 2019 at 11:11 AM David Arnold <davida@pobox.com> wrote:

> On 2 Aug 2019, at 09:43, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>
> > Speaking of LISP and GC, it's impressive how GC is not really a big
> issue any
> > more. At one point people were even building special CPUs that had
> hardware
> > support for GC; now it seems to be a 'solved problem' on ordinary CPUs.
>
> I think it’s mostly a side effect of modern hardware speeds. For
> applications that care about latency (and especially latency jitter) it’s
> still an issue.
>
> For example, writing low latency trading software in Java requires some
> fairly silly hoop-jumping to avoid triggering a collection pass.
>
> These apps genuinely care about nanoseconds, but the tooling ecosystem and
> development time advantages of Java seem to entice a decent number of
> people to embark on the work-arounds.
>
> In most areas though you’re absolutely right — it’s a non-issue now.
>
>
>
> d
>

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

  reply	other threads:[~2019-08-02  4:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-01 23:43 Noel Chiappa
2019-08-02  1:03 ` David Arnold
2019-08-02  4:36   ` Rob Pike [this message]
2019-08-07  2:35 ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2019-08-02 14:35 Noel Chiappa
2019-08-02 15:01 ` Clem Cole
2019-08-02 15:17 ` Arthur Krewat
2019-08-02 21:23   ` Dave Horsfall
2019-08-03 12:51     ` Nemo
2019-08-01 12:35 Doug McIlroy
2019-08-01 16:22 ` John P. Linderman
2019-08-01 16:35   ` Arthur Krewat
2019-08-01 17:01 ` Nemo Nusquam
2019-08-01 18:26   ` Arthur Krewat
2019-08-01 20:14     ` Lyndon Nerenberg
2019-08-01 21:23 ` Dave Horsfall

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='CAKzdPgxNjCEdEOu4b06AKLfzLB0GLphu71M8g=XFRpjRSz7yhw@mail.gmail.com' \
    --to=robpike@gmail.com \
    --cc=davida@pobox.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --cc=tuhs@tuhs.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).