From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <826abb8cf0c1ea41e3ebc081df3169c7@proxima.alt.za> Date: Fri, 14 Sep 2012 15:26:25 +0100 Message-ID: From: Charles Forsyth To: erik quanstrom Content-Type: multipart/alternative; boundary=0016e6d56374771e3604c9aa350e Cc: 9fans@9fans.net, lucio@proxima.alt.za Subject: Re: [9fans] Acme: the way the future actually was Topicbox-Message-UUID: b93d09ac-ead7-11e9-9d60-3106f5b1d025 --0016e6d56374771e3604c9aa350e Content-Type: text/plain; charset=UTF-8 "Copy" is a little strong: inspired by, certainly, by way of help/help, but there's an amazing difference in the structure of acme as "text editor as file server" with many independent clients accessing it through the file system. Oberon had a more conventional module "plug-in" structure within a single process. Acme's user interface is also more strictly text-oriented, and streamlined the mouse conventions. On 14 September 2012 15:19, erik quanstrom wrote: > neither is knowledge of oberon ubiquitous among 9fans, who may > not realize that acme itself is a copy. > --0016e6d56374771e3604c9aa350e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable "Copy" is a little strong: inspired by, certainly, by way of help= /help,
but there's an amazing difference in the structure of acme a= s "text editor as file server"
with many independent cl= ients accessing it through the file system.
Oberon had a more conventional module "plug-in" structure wi= thin a single process.
Acme's user interface is also more str= ictly text-oriented, and streamlined the mouse conventions.

On 14 September 2012 15:19, erik quanstrom <quanstro@quanstro.net> wrote:
neither is knowledge of oberon ubiquitous among 9fans, who= may
not realize that acme itself is a copy.

--0016e6d56374771e3604c9aa350e--