🚀 go-pugleaf

In article <C0MKEu.5or@poel.juice.or.jp>, erik@poel.juice.or.jp (Erik M. van der Poel) writes:
> 
> The way I see it, Plan 9 is itself an island.

I'm not sure at all that Plan 9 _is_ an island;  utf and 9P have been
published, you can actually read all of the documentation and understand
it (in contract to things like X and the almost unbounded number of RFC's),
it's more `open' than anything else that goes by the same moniker.

Reminds me of Geoff Collyer's comment [in ;login:] that the [PDP] 11/70 was
`open' because you could get the documentation, read it and build something.
It seems that the wheel has turned full circle in that it's again difficult
to build things because of the intentional (or otherwise) complexity,
obscurity and the broken set of tools to hand.

And while I'm at it, I think that GNU are as much a part of the problem rather
than the solution.  Yes you can get the source, but it's of no use because
it has been crippled by comlexity.  Look at gcc: a zillion command line
options when it should probably have _less_ than 5; the compiler should
just compile a program that adheres to the language spec, no more, no less.

So, what's my plan?  Talk utf and 9P and get some connectivity happening.
TCP/IP access to a public 9P file-server would be a start.  I'd almost be
tempted to `teach' NFS about 9P.  Yes, I'm probably that crazy.


Boyd Roberts			boyd@prl.dec.com

``When the going gets wierd, the weird turn pro...''