From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <9front-bounces@9front.inri.net>
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=HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4
Received: from 9front.inri.net (9front.inri.net [168.235.81.73])
	by inbox.vuxu.org (Postfix) with ESMTP id 40F90240E3
	for <ml@inbox.vuxu.org>; Wed,  8 May 2024 16:10:11 +0200 (CEST)
Received: from gaff.inri.net ([168.235.71.243]) by 9front; Wed May  8 10:04:08 -0400 2024
Received: from [127.0.0.1] ([168.235.81.125]) by gaff; Wed May  8 10:04:08 -0400 2024
Date: Wed, 08 May 2024 10:04:06 -0400
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
In-Reply-To: <CAFSF3XPkC+QLas0sNsYXAa_mOwuVZ9nwYGctFk_DaXrDJ6g_9Q@mail.gmail.com>
References: <102b2835-4207-4f8c-9f29-9da8b459dc2e@posixcafe.org> <5CF629DBC32C6D8D674AE2E07A2F8289@gaff.inri.net> <CAFSF3XPkC+QLas0sNsYXAa_mOwuVZ9nwYGctFk_DaXrDJ6g_9Q@mail.gmail.com>
Message-ID: <37F17A13-D66F-496A-A36B-177C0B7E8AEB@stanleylieber.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: generic abstract CSS-scale factory NoSQL database 
Subject: Re: [9front] Enabling a service
Reply-To: 9front@9front.org
Precedence: bulk

On May 8, 2024 3:22:25 AM EDT, hiro <23hiro@gmail=2Ecom> wrote:
>> the laptop thing in particular is
>> always funny to me, because in practice it's very similar to that old
>> situation where bell labs people had slow connections to their terminal=
s
>> at home=2E it's too bad ancient terminals weren't battery powered, or
>> maybe the plan 9 gods would have already put some thought into this=2E
>
>I believe this must have been a party trick mostly=2E They were likely
>still required to show up in the office=2E
>
>The latency of these connections was very good, so that's how I
>explain their lack of optimizations in rio for limiting the amount of
>roundtrips=2E
>Or they used an older version that didn't have the very slow rio yet=2E
>And obviously mostly everything was text back then, so no need to fix
>the roundtrip-bottleneck for high bitrate media like images=2E
>
>If they had our use-case, I don't know if they would have gone for the
>kind of optimization that I have in mind, as this leads to diminishing
>returns very fast=2E Fully meshed, non-centralized distributed systems
>might be too juicy for them to ignore for solving this kind of
>problem=2E
>

yeah, i was thinking of the blit vs the first eight unix guis, jim/sam, et=
c=2E

sl