Re: [xml-dev] How to design XML to have broad utility and yet also enable efficient application processing?

From
Ihe Onwuka <>
To
Rick Jelliffe <>
Date
2013-11-21T08:51:32Z
ID
<>
Thread
Re: [xml-dev] How to design XML to have broad utility and yet also enable efficient application processing?
On Thu, Nov 21, 2013 at 2:18 AM, Rick Jelliffe <> wrote:
> Knuth was wrong about avoiding premature optimization. Because there is now
> a generation of coders who take him to mean that you should initially ignore
> performance or implementation heuristics or real-time aspects and
> concentrate on correctness. The result is systems that fall over in
> certification or integration testing.
>

Actually one can concretize this principle with your everyday XSLT
transformation.

How many times have you combined a bunch of patterns into a single
template rule by unionising the match attribute (premature
rationalisation) only to subsequently find there is actually some
nuance that doesn't apply to one or more of  the patterns you
combined?

Never. None.

Hmmm must be just me then.