Received-SPF: neutral (google.com: 192.0.33.81 is neither permitted nor denied
 by best guess record for domain of tz-bounces@iana.org)
 client-ip=192.0.33.81;
Date: Thu, 12 Sep 2013 12:07:45 +0100
From: Zefram <zefram@fysh.org>
To: tz@iana.org
Message-ID: <20130912110745.GE31643@fysh.org>
References: <52303DFC.1070309@cs.ucla.edu>
 <1378902513.30165.20632105.13D787EC@webmail.messagingengine.com>
 <20130911125056.GY31643@fysh.org>
 <1378905291.15942.20645633.2B8D634C@webmail.messagingengine.com>
 <20130912023552.GB40119@davros.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130912023552.GB40119@davros.org>
Subject: Re: [tz] Getting close to new release: testing, testing, ...
Precedence: list
Sender: tz-bounces@iana.org
Errors-To: tz-bounces@iana.org
Status: RO

Clive D.W. Feather wrote:
>What's wrong with XML.

It's hideously verbose; it doesn't actually provide a representation
of the data (it only provides structure); it has awkward corners that
end up poorly tested; as it's a textual format it's subject to all the
usual problems around character sets; the context encourages the use of
forgiving parsers for the actual textual data representation, which leads
to incompatibility; and it's a bad design in the first place because it
tries to tackle too many classes of job.

-zefram