From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam vs acme
From: forsyth@caldo.demon.co.uk
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20010720224617.4D54E199DC@mail.cse.psu.edu>
Date: Fri, 20 Jul 2001 23:41:54 +0100
Topicbox-Message-UUID: d2782cfc-eac9-11e9-9e20-41e7f4b1d025

>>Does this mean that every interactive display program that
>>does large amounts of file I/O but has low information theoretic
>>bandwidth to the display (e.g. editors, spreadsheets, just
>>about anything but pictures in fact) should be written in a
>>split-process style similarly to sam?  Isn't that a pretty
>>big burden for programmers?  Isn't there some way to solve this
>>problem *once* and reuse the solution?

yes.  consider exporting a computable name space.

i've found it often reduces the burden on the programmer,
offers natural places to split the task, and like interconnection
with pipelines in unix, allows unusual combinations not expected
initially.