W3C home > Mailing lists > Public > public-html-xml@w3.org > January 2011

Re: Improving XSLT in the browser, was: Use cases

From: Michael Kay <mike@saxonica.com>
Date: Tue, 04 Jan 2011 00:04:18 +0000
Message-ID: <4D226402.4000809@saxonica.com>
To: Julian Reschke <julian.reschke@gmx.de>
CC: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, John Cowan <cowan@mercury.ccil.org>, Norman Walsh <ndw@nwalsh.com>, public-html-xml@w3.org
On 03/01/2011 21:54, Julian Reschke wrote:
> On 03.01.2011 01:31, Benjamin Hawkes-Lewis wrote:
>> ...
>> If the root problem addressed by Use Case 4 is developers want easier
>> ways to generate views from models expressed in XML, maybe energies
>> should be redirected from fiddling with text/html parsing to
>> investigating how XSLT could be improved so it doesn't suck so hard. Why
>
> It doesn't suck at all. :-) But of course it would be great to make 
> improvements.

We really need to recognize that different programming languages suit 
different kinds of user and different kinds of task. XSLT suits some 
users and some tasks rather well, and others rather badly. In critiquing 
technologies, we need to be a bit more scientific than sticking "rocks" 
or "sucks" labels on things.

We need to move away from the assumption that we can create a single 
toolset, with no overlaps, that will meet all functional and 
psychological requirements. It's like expecting everyone to drive the 
same kind of car. The platform needs to be heterogeneous and extensible: 
we need to design a shared road infrastructure that can accommodate a 
wide variety of individual vehicles specialized to different purposes or 
aspirations.

Michael Kay
Saxonica
Received on Tuesday, 4 January 2011 00:04:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 4 January 2011 00:04:49 GMT