Subject: Re: [xsl] New XSLT 3.0 Working Draft From: Michael Kay <mike@xxxxxxxxxxxx> Date: Thu, 12 Jul 2012 18:37:46 +0100 |
One thing we haven't really looked at yet is profiling. Before the spec is carved in stone, I would expect us to define some features (such as streaming, packages, maybe higher-order-functions) as optional. That will hopefully leave a spec which is still a useful advance for the mainstream user (with things like maps, try/catch, and evaluate) while not being vastly expensive for an existing XSLT 2.0 implementation to upgrade to.I think Tommie says this well. But rather than focus on the unsupported (and IMHO likely to be untrue) premise, I'd like to focus for a moment on the question: "what are the chances of 3.0 being adopted"?
My thoughts on this are
* while for users like me the advancements in 3.0 are way cool, but not particularly important,
* for users like Google and Amazon who have *lots* of data, the streaming capability of 3.0 will make it very attractive,
* users like Google and Amazon have money and resources, where users like me don't,
* it's extremely likely that at least 1 major implementation (Saxon)
will support 3.0,
I think it pretty likely that 3.0 will have widespread adoption as a
programming language and for use server-side. I doubt it will have
any feet in-the-browser.
Michael Kay Saxonica
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] New XSLT 3.0 Working Draf, Syd Bauman | Thread | Re: [xsl] New XSLT 3.0 Working Draf, Ihe Onwuka |
Re: [xsl] New XSLT 3.0 Working Draf, Syd Bauman | Date | Re: [xsl] New XSLT 3.0 Working Draf, davep@xxxxxxxxxxxxx |
Month |