From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <2863EB61-78FF-4E15-B30B-F94A28613663@orthanc.ca>
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-Reply-To: <201105061647.36343.errno@cox.net>
Content-Type: text/plain;
	charset=us-ascii;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPod Mail 7E18)
Date: Fri,  6 May 2011 17:12:02 -0700
References: <b95d02898da2669c36cd10f59df1929e@terzarima.net>
	<44c5b39f47469ed34fefaf5f4f6f7c2e@brasstown.quanstro.net>
	<BANLkTimCzp+sBfT6C2JvLsrGX8Ecz_R+7g@mail.gmail.com>
	<201105061647.36343.errno@cox.net>
Subject: Re: [9fans] Compiling 9atom kernel WAS: Re: spaces in filenames
Topicbox-Message-UUID: e01cfc40-ead6-11e9-9d60-3106f5b1d025


> A veneer of html + css + javascript over the intrinsically distributed
> foundations of Plan 9, would provide the bridge for an entire class of
> use-cases currently out of reach:

Speaking in platitudes doesn't make a case. How specifically would
this tie in to 9p? How specifically does it fit into namespaces? Show
us some code fragments. Write some simple file servers to stub out
this veneer you describe.

In the process of doing this you will learn a lot about plan 9. And as
a side effect, you will come to understand why nobody else has gone
down this road.