Re: [whatwg/dom] Proposal - Update XPath to (at least) v2.0 (#903)

Also, knowing some of the people involved - I think discussion here isn't too great:

 - Having a lot of people show up downvote/upvote things isn't great. It's a shame GitHub doesn't let repo owners turn that feature on/off. It creates a feeling of maintainers being attacked.
 - "Chrome is not interested in this" is a perfectly fine way to respond. You may not _like_ the fact Domenic said that nor that it's Chrome's position _but_ Chrome is allowed to have that position. I think a productive follow up would have been "what would it take for you to reconsider?" or "how can we help with Chrome's concerns?" or something similar.
 - Telling Chrome about libraries ( like saxon-c ) doesn't help. It's asking them to allocate a significant amount of work to refactor a feature _they are not interested in maintaining to begin with but have to_. It'll be a _very_ hard sell.
 - Props to Andrea for trying to engage constructively and actually explain _why_ XPath2 would be useful for Chrome and what capabilities it adds to the web platform that may ask Chrome to support it. Also props to Liam on explaining why that's good.

I am not sure why no one brought up the fact that XPath 3 implementations exist in userland ([this seems to be the most popular one](https://github.com/FontoXML/fontoxpath)) but they are not popular. So XPath 3 does not add capabilities to the web platform since it's possible in userland and is not popular and does not fix the issues with the existing APIs since it can't replace it because of compatibility.

If you want to engage (constructively) with Chrome on this - you need to look at their perspective and explain how an investment into XPath 3.1 aligns with their goals. For example - get someone to sponsor work that reduces the existing technical debt significantly while adding the API. TBH if I were Chrome I'd likely still not go for it because of their perspective.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/903#issuecomment-720132911