From: David Arnold <davida@pobox.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Who's behind the UNIX filesystem permission
Date: Fri, 2 Aug 2019 11:03:34 +1000 [thread overview]
Message-ID: <A7F61221-47D0-4A21-82FC-F0201F085990@pobox.com> (raw)
In-Reply-To: <20190801234351.04A9118C0A1@mercury.lcs.mit.edu>
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
next prev parent reply other threads:[~2019-08-02 1:10 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 [this message]
2019-08-02 4:36 ` Rob Pike
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=A7F61221-47D0-4A21-82FC-F0201F085990@pobox.com \
--to=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).