I think the real reason Microsoft aren't
investing in XSLT is that they
aren't making any money out of it, which
is because they can't compete with
free software. There are plenty of XSLT
enthusiasts inside the company, as
the blog indicates, but they don't have
any funding.
Well this was one of the things that I saw
as the reason for the complexity of the new
wd, if it becomes complex enough you weed
out the competition.
The sad part of this is that it pretty
well kills XSLT on the browser, which
always held out so much promise if only
the interoperability problems could
be sorted out.
I don't know if it kills XSLT on the
browser. There is I assume still quite a
long time before MS will release any browser
that is .net based.
XQuery in its current form is no good at
document transformation, and even
for data, it's got much less functionality
than XSLT 2.0. It will succeed as
a database query language, which is what
it's designed for, but I don't
think it will ever threaten the space
where XSLT is currently used.
I don't know, success of a language is often
tied to developer intuition of its future
viability, lack of Windows support makes for
an argument against such viability for some
people. It's a hit, not a knockout. hmm,
maybe it's only a slap, but I feel hurt.
:(