From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id d34bdb47 for ; Fri, 2 Aug 2019 04:37:34 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 8DC469BAAB; Fri, 2 Aug 2019 14:37:33 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 0E5FE9BA80; Fri, 2 Aug 2019 14:37:03 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="LQbtH4eg"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 165F89BA7E; Fri, 2 Aug 2019 14:37:00 +1000 (AEST) Received: from mail-vk1-f172.google.com (mail-vk1-f172.google.com [209.85.221.172]) by minnie.tuhs.org (Postfix) with ESMTPS id 77F789B84E for ; Fri, 2 Aug 2019 14:36:59 +1000 (AEST) Received: by mail-vk1-f172.google.com with SMTP id f68so15100689vkf.5 for ; Thu, 01 Aug 2019 21:36:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nM+8BUHC2S1wwOZgkMM98zg9/vJ/RTCDktYFxD9kXVs=; b=LQbtH4egxjKHCeWJh/Z8Emo5kGpOBe+bWteM5JeY3cSUHg46WPYxpbj1VbQzi3fABB mEhXnKQpqObxWzfM8kLw87M/Tf+64qTkZm71TNakj/V5OaL0UPwRWCDrgBWcjvCrmS/j j4MqMFoOkoajE/AQkHtKFiALTfb29/mh78ffJo2AU6WAWM+WZP0ANdImcbvmtSsjRUVD y3g5Xywx7XIj5cEhxy18fq+/4ev27Mo8kZ7mcoHJTe+vtMXJMc6cKhrPkfr7tzbT+ixC Mpjw7/3/rdiR4voMkqR76wz/tG8NHlVJQ2iUjkbk/CwJRg6Z8rv7N68Z05MEtoOHZ0RE bDFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nM+8BUHC2S1wwOZgkMM98zg9/vJ/RTCDktYFxD9kXVs=; b=YE15YaR2HIP22FmMkneJ45+nicKfTGX/tqNNAzqw+s0N3/h88UGYQdhErYYWaU2Wi3 C4L5Ju71QdsyJJSf9u6QjVVvgUgquWccTOdOLFZBY71Pex7Vu3wtTUK/TQYhkJJWNG0/ pqd+r8AVT85rJusv3D0QoUXr0uaZ2gIHJwToUiOD73JDx1mhnFOqSHvEbBOaoamNs3Tn df2oHEXlMa5wg+BYnibYaWH0pzBIej5JcWjlofFdRIsShkgX2ooP97gF8YlOLfPw5KBh v/ZZAF/ESr4m+E07tK3b2VVZ1kKOZgNsz869TY8CuQgRF/D4llupXmmjADumSvHuGZ36 jmeA== X-Gm-Message-State: APjAAAX9Qe+nzyMHxZICs6+f+VekuGamfHyjalwTtOhcjQD9muWlj9+u ZW6TCpkFBRtM/FuLnE4Tb3kwa7mjpLmT3YODhgA= X-Google-Smtp-Source: APXvYqwtcW7GLnV1VB48C66jUCDiY1Ux4j3A2jMuaxj2oGptwVTPqC4dVOP2/ZnTDysAyyt/TRCNAtLjE3g057VAaqg= X-Received: by 2002:ac5:c7ce:: with SMTP id e14mr18418777vkn.61.1564720618393; Thu, 01 Aug 2019 21:36:58 -0700 (PDT) MIME-Version: 1.0 References: <20190801234351.04A9118C0A1@mercury.lcs.mit.edu> In-Reply-To: From: Rob Pike Date: Fri, 2 Aug 2019 14:36:47 +1000 Message-ID: To: David Arnold Content-Type: multipart/alternative; boundary="000000000000a1d578058f1ae8ba" Subject: Re: [TUHS] Who's behind the UNIX filesystem permission X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society , Noel Chiappa Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000a1d578058f1ae8ba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 wrote: > On 2 Aug 2019, at 09:43, Noel Chiappa 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=E2=80=99s mostly a side effect of modern hardware speeds. For > applications that care about latency (and especially latency jitter) it= =E2=80=99s > 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 an= d > development time advantages of Java seem to entice a decent number of > people to embark on the work-arounds. > > In most areas though you=E2=80=99re absolutely right =E2=80=94 it=E2=80= =99s a non-issue now. > > > > d > --000000000000a1d578058f1ae8ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
In Go we "just" dedicate a core to GC, problem s= olved. The arrival of universal multi-CPU hardware made than option. Some t= remendous technical work required (for which I take zero credit; see=C2=A0<= a href=3D"https://blog.golang.org/ismmkeynote">https://blog.golang.org/ismm= keynote) 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&g= t; wrote:

> Speaking of LISP and GC, it's impressive how GC is not really a bi= g issue any
> more. At one point people were even building special CPUs that had har= dware
> support for GC; now it seems to be a 'solved problem' on ordin= ary CPUs.

I think it=E2=80=99s mostly a side effect of modern hardware speeds. For ap= plications that care about latency (and especially latency jitter) it=E2=80= =99s still an issue.

For example, writing low latency trading software in Java requires some fai= rly 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 peopl= e to embark on the work-arounds.

In most areas though you=E2=80=99re absolutely right =E2=80=94 it=E2=80=99s= a non-issue now.



d
--000000000000a1d578058f1ae8ba--