From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 20487 invoked from network); 11 Aug 2021 18:12:18 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 11 Aug 2021 18:12:18 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 0C4F7947B8; Thu, 12 Aug 2021 04:12:12 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id D91A094680; Thu, 12 Aug 2021 04:11:39 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; secure) header.d=hamartun.priv.no header.i=@hamartun.priv.no header.b="kGfJnFFl"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 39F1594680; Thu, 12 Aug 2021 04:11:35 +1000 (AEST) Received: from barsoom.hamartun.priv.no (barsoom.hamartun.priv.no [193.71.27.8]) by minnie.tuhs.org (Postfix) with ESMTPS id 0D9AE9467E for ; Thu, 12 Aug 2021 04:11:33 +1000 (AEST) Received: from thuvia.hamartun.priv.no (thuvia.hamartun.priv.no [IPv6:2001:8c0:c904:10::7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by barsoom.hamartun.priv.no (Postfix) with ESMTPS id 4GlHvN69RgzG2Xb; Wed, 11 Aug 2021 20:11:28 +0200 (CEST) Authentication-Results: barsoom.hamartun.priv.no; arc=none smtp.remote-ip=2001:8c0:c904:10::7 ARC-Seal: i=1; a=rsa-sha256; d=hamartun.priv.no; s=barsoom; t=1628705489; cv=none; b=i4F6S39JroG+v4X+5SMKA27NV4ZcTOQeDCdkJdIlRqQnJsP3mvmCXe9yV8xox0IXlLHL+PvvphRsdyhvCHhCBS+l0VoZ7+fFaQl/4Z8AY+M5sz+KYquCQr9Dj06KZR+TZWSkLrbVv29MkHK8z2amjF3HlKMUYUSN8Py0UeXxn+s= ARC-Message-Signature: i=1; a=rsa-sha256; d=hamartun.priv.no; s=barsoom; t=1628705489; c=relaxed/simple; bh=ZR8kzE2+65Nrzi/Hl3dMVxPLvRTr6tp5g/kqdKDC0p4=; h=DKIM-Signature:Received:From:To:Cc:Subject:References:Date: In-Reply-To:Message-ID:User-Agent:MIME-Version:Content-Type; b=St3SfxFwXaA9rfccct4GhtZJ3bwjK7ZVSmExOacSwiXA5C/oJU3+p34+q1L4bOXJYdfNg10H40hQY0shCFZHyzikaxidafN7PmQvS5RuOvEA8PWoiZ8GrkCwdFYYU9MshfXM+KbxI+AHKW9ifEvwboi9RCsz0WUBrwymsT9sM7k= ARC-Authentication-Results: i=1; barsoom.hamartun.priv.no DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hamartun.priv.no; s=20200727; t=1628705489; bh=ZR8kzE2+65Nrzi/Hl3dMVxPLvRTr6tp5g/kqdKDC0p4=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=kGfJnFFlnHsoh8NKDuRhLVx09MvOademjQfmOhZaAxnk0YwArpKjeDdujzLo7rmW9 UIHM5Nl3eXn+aCv4nu8VAOisVTLDHd2gtagK3kAPX4lMJxcz/rTQfBMjJWGlzDDN8Z gvIocGZe+0K1R3ZeqPd5siKGUTb1fZhVtatswXveU49RSm91FokXB/Xh2YIGcuzkxr 3jRhuc1U5pWabvJ7Ua6PkbvpdkeTJFz1ssyHCvjkTb5Y6KH0rHXIth38Y0vt8jBwTf EqDPygOSh6+Daw/0/QZ/e4QkoBdvsRVtFb3BKJa0sLn7X/sqxb8g0pVNmdy5sEMNNJ kamy4X8evwkKw== Received: by thuvia.hamartun.priv.no (Postfix, from userid 501) id 5C5684DF08; Wed, 11 Aug 2021 20:11:28 +0200 (CEST) To: Tom Lyon via TUHS References: Date: Wed, 11 Aug 2021 20:11:28 +0200 In-Reply-To: (Tom Lyon via TUHS's message of "Tue, 3 Aug 2021 10:13:31 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [TUHS] Systematic approach to command-line interfaces 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: , From: Tom Ivar Helbekkmo via TUHS Reply-To: Tom Ivar Helbekkmo Cc: The Eunuchs Hysterical Society , Douglas McIlroy Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" Tom Lyon via TUHS writes: > What if CPU designers would add facilities to directly implement > inter-process or inter-processor messaging? You mean like INMOS's Transputer architecture from back in the late eighties and early nineties? Each processor had a thread scheduling and message passing microkernel implemented in its microcode, and had four bi-directional links to other processors, so you could build a grid. They designed the language Occam along with it, to be its lowest level language; it and the instruction set were designed to match. Occam has threads and message passing as built-in concepts, of course. -tih (playing with the Helios distributed OS on Transputer hardware) -- Most people who graduate with CS degrees don't understand the significance of Lisp. Lisp is the most important idea in computer science. --Alan Kay