i guess the non-inflammatory title would be “representative of chrome project votes no in one of many working group proposals “?
Chrome unlikely to support XPath 3.1
11–20 of 114 posts
Re: Chrome unlikely to support XPath 3.1
#12Re: Chrome unlikely to support XPath 3.1
#13Please just let XML die. Just because it existed doesn't mean it has to exist forever. Will there be pain points in getting rid of it for good? Yeah. But we'll be better off in the long run.
Re: Chrome unlikely to support XPath 3.1
#14No one addresses why the company that dominates web search should have an outsize influence on standards in an area where it has an obvious conflict of interest in adopting technologies that _may_ empower potential competitors, aka ie the rest of the world.
Re: Chrome unlikely to support XPath 3.1
#15As 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.
Re: Chrome unlikely to support XPath 3.1
#16I feel like XPath queries have been gaining more widespread usage over the last decade by developers at the css/javascript level, so perhaps it makes sense to improve the power of it.
Re: Chrome unlikely to support XPath 3.1
#17Safari 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.
Don’t let perfect be the enemy of good. Use MathML, put up noticea that your content only works in Safari and Firefox. These are all attacks against Google. FIGHT!
Re: Chrome unlikely to support XPath 3.1
#18Let’s deprecate old technologies that are currently bundled in web browsers instead of adding to them. Browsers need to go on a diet.
browsers are quite fast nowadays.
they appear to be bloated mainly because of two reasons:
1) companies pulling in all sort of un-optimized content and making requests to a huge amount of external services, effectively slowing down the render of pages
2) a lot of developers developing stuff that should really be native code in html+js+css, which doesn't always perform that well and tends to slow down the whole browser. it really suffices one badly-coded app (not using well asynchronicity and/or wasting memory) to make the whole browser appear slow.
Re: Chrome unlikely to support XPath 3.1
#19This discussion is a decade late. The direction was set when HTML5 was chosen instead of XHTML 2.0 and I don't think any important group changed their mind since. Committee-made standards are impotent without popular implementations.
Re: Chrome unlikely to support XPath 3.1
#20As 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.
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.