It was purely a light hearted comment.
Seriously though I don't think client-side transformations are ever going be a serious prospect, especially using version 2.0, unless it's an intranet or similar scenario whereby you have control to dictate the browser.
Even then it seems quite some way off. The nearest I've seen are some of the XAML demos but they need a hefty install at the moment so popular take up is still a year away at least.

--

Joe (Microsoft MVP - XML)

Hi Joe,

> It was purely a light hearted comment.

Great. I'm pleased to hear that :-)

And thanks for your thoughts on the chances of XSL 2.0 arriving.

Indeed, I am developing/discovering tricks and techniques for working with XSL 1.0 so now I know that I should stick with that (for the time-being).

Anyway, I'm curious to see what comes and will keep my eye on developments.

Cheers,
Alan.

XSLT 2.0 provides much easier-to-use grouping facilities, but it still doesn't allow for dynamic expression evaluation (that is, expressions constructed at run-time as a string, or read from source documents. You still need extensions such as saxon:evaluate() for that.

But as I think Joe mentioned, so long as you're using XSLT client-side you have to wait for the browser vendors to supply the technology you need, and since no-one is making any money by selling browsers that can take an increasingly long time.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference