Hacker News Reader

XML for document content (like, the whole point of markup) = awesome.

XML for app configuration or basic data transfer formats = horrible.

Unfortunately I fear so many people got burned by the latter issues they forgot (or missed entirely) all the greatness of the first.

View on HN

I agree that XML is much better for document content and markup than for configuration and other stuff. I think still there are problems with XML, although that problem can be avoided (and often is, now, since JSON is often used instead, but JSON has its own problems, too).

P.S. Google has a bazillion dollars but can't figure out how to maintain a new secure XSLT library or update to a newer one which exists already? The usage argument is dumb…maybe a lot more sites would find good uses for XML/XSLT if this stuff was actually maintained and promoted properly!

Why would Google want to bother? Who actually uses XSLT today for making webpages? Why should browsers spend effort on supporting XML+XSLT-based pages in addition to HTML+CSS-based pages?

Reply on news.ycombinator.com