back

by zorked·5y ago·view on hn ↗
This is an editorialized link name and the target comment isn't even obviously wrong or anything. Let the awfully outdated XML tooling die.

Context: This was named "Chrome holding the web back: an example", I expect moderation will change this at some point to something like "Chrome unlikely to support XPath 3.1" which is considerably less incendiary and something few people here care about.

1 comments
More like: "Chrome unlikely to follow WHATWG XPath 2.0+ support spec if ever merged"

Or "Chrome devs being against XPath 2+ spec because of internal maintenance problems"