From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <13426df10705210957w2982fa31lc6c22ff554fcd629@mail.gmail.com>
Date: Mon, 21 May 2007 09:57:46 -0700
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [9fans] XML
Topicbox-Message-UUID: 6c68718e-ead2-11e9-9d60-3106f5b1d025

This one is interesting:
"The acmpolicy class implements a compiler for translating an XML policy
into their binary format and provides functionality for comparing a
current policy against a new one when changing a policy."

So, translate XML to binary to use it?

But it's a standard, right? I can't tell you how many times a day
people tell me they're doing something in XML ... "it's the standard"
-- not "A", but "THE".

Let's see:

<9p><request>T</request><requesttype>R</requesttype><fid><number><digit><binary>1</binary><binary>0>/binary>...


well, you get my drift.

Shouldn't we move 9p to a standards-based, compliant, XML-based system
with first-class enumerated elements in which all pluggable components
are Python objects and hence first-class citizens and add a full
compiler to enable translation and XML co-processor acceleration?

Can I randomly permute the words in the previous sentence? Yes.
Is that sentence like stuff I read nowadays? Yes.
Is constant gnashing wearing off the enamel on my teeth? Yes, oh yes.

ron