From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sat, 11 Feb 2006 11:28:27 -0500
From: Dan Cross <cross@math.psu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] asn.1 alternatives
Message-ID: <20060211162827.GR1620@augusta.math.psu.edu>
References: <11d846ba1d1323cc1e956b2f67dfa6ec@plan9.bell-labs.com>
	<541ac7952476f11c319d81a7b9f7d516@terzarima.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <541ac7952476f11c319d81a7b9f7d516@terzarima.net>
User-Agent: Mutt/1.4.1i
Topicbox-Message-UUID: fc20884a-ead0-11e9-9d60-3106f5b1d025

On Sat, Feb 11, 2006 at 02:29:19PM +0000, Charles Forsyth wrote:
> also, in my experience, managers (pointy-head or not) are rarely overly
> caught up by the technical details.  they just want such-and-such a problem
> to go away.  they usually don't really care how you do it, especially if it
> works well and they never ever have to cut short a trip to the golf course
> because of it.

I think, perhaps, that this is less true than it once was.  In particular,
they need to answer to marketting and ensure that the product is sufficiently
buzzword compliant.  But my point in bringing up the managerial team in the
first place was just to demonstrate that sometimes the person doing the
implementation doesn't *really* have all that much control over the choices
made for the implementation.  An extreme example would be, say, if I were
writing a Windows application.  I probably don't have much ability to write
it for another system (Unix, Plan 9, whatever) instead because I'd prefer
that.

As for ASN.1 alternatives....  When you have a choice, I would agree that
S expressions are compelling.  Another option is YAML, which is becoming
popular in the scripting language world, and is fairly reasonable, even for
representing complex hierarchical objects.

	- Dan C.