Live data from Hacker News

Chrome unlikely to support XPath 3.1

github.com

31–40 of 114 posts

Re: Chrome unlikely to support XPath 3.1

#31

As of the last couple years, Chrome is the web. The writing has been on the wall since at least Widevine. The browser wars are over, and I don't see any scrappy startup crossing the moat of complexity GOOG has built around "modern" browsers. Especially when combined with their stranglehold of the standards committees. We need to find a new attack vector.

Things looked similar amid the dominance of IE. I think it will probably happen eventually, though you're right that a start-up probably won't do it. The problem that no one pays for web browsers. There are companies building alternative engines for commercial embedding (including one that's parallel and very fast), so it would probably involve one of those being open-sourced.

Re: Chrome unlikely to support XPath 3.1

#32

Safari tends to be slow to implement features, but they rarely outright reject implementing a feature. Google Chrome hasn't implemented MathML yet, even though Firefox and Safari have: https://caniuse.com/mathml

The MathML support in Firefox and Safari are barely usable. Even if my target audience all browsed on Firefox and Safari, I'd avoid MathML.

It looks quite capable:

https://mdn.mozillademos.org/en-US/docs/Mozilla/MathML_Proje...

https://mdn.mozillademos.org/en-US/docs/Mozilla/MathML_Proje...

https://mdn.mozillademos.org/en-US/docs/Mozilla/MathML_Proje...

Re: Chrome unlikely to support XPath 3.1

#33
I mean some people working on Chrome tried to remove XSL support at some point:

https://bugs.chromium.org/p/chromium/issues/detail?id=514995

which was already nuts, so they are clearly not interested in anything related to XML. XML is a fantastic tool, it's just that a whole generation of developers refused to even touch it and are biased against it.

And since Chrome is now basically the web... wait til there is only Chrome and Safari left and see what happens to web "standards"...

Re: Chrome unlikely to support XPath 3.1

#35

Safari tends to be slow to implement features, but they rarely outright reject implementing a feature. Google Chrome hasn't implemented MathML yet, even though Firefox and Safari have: https://caniuse.com/mathml

Safari has been holding the web back for years on features that make the web competitive with Apple's app ecosystem. I don't believe the distinction of "rejecting" vs being slow has merit.

https://caniuse.com/push-api https://caniuse.com/mediasource

Re: Chrome unlikely to support XPath 3.1

#36
post #30

Earlier quoted context omitted.

They’ll do it to themselves. One thing I see regularly is Chrome’s web caching being so aggressive it is driving front-end developers to start using FF for dev. We simply need to stand back and let time take its course.

Does Chrome no longer have the option to disable cache while dev tools is open?

It does have it. I personally often use Firefox for the css grid and flexbox tools but they're very similar in functionality.

Re: Chrome unlikely to support XPath 3.1

#37

Safari tends to be slow to implement features, but they rarely outright reject implementing a feature. Google Chrome hasn't implemented MathML yet, even though Firefox and Safari have: https://caniuse.com/mathml

Apple has refused to implement a large number of features, at least as many as Google. They're usually more quiet about it though unless it's part of marketing related to privacy. All the browsers take strong architecture and ecosystem positions.

Re: Chrome unlikely to support XPath 3.1

#39
post #11

i guess the non-inflammatory title would be “representative of chrome project votes no in one of many working group proposals “?

They didn't just vote no. They basically said they're not implementing it even if everyone else votes yes.

Like my mother used to say: if all of your friends jumped off a bridge, would you jump too?

Re: Chrome unlikely to support XPath 3.1

#40

Safari tends to be slow to implement features, but they rarely outright reject implementing a feature. Google Chrome hasn't implemented MathML yet, even though Firefox and Safari have: https://caniuse.com/mathml

Actually, they do refuse sometimes, not that I’m against it, but it’s inaccurate to say they don’t.

https://www.zdnet.com/article/apple-declined-to-implement-16...

Post reply on HN