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

@domenic I am not sure that "*folks*" included me (but I guess so ...)

> I can tell this is not going to be a productive conversation, as folks intent are playing word games

I honestly had the feeling there was no room for any conversation, after your first reply:

> Chrome is not interested in this. The XML parts of our pipeline are in maintenance mode and we would love to eventually deprecate and remove them

although, this sentence is both *not* exactly what I've proposed, but also scary, 'cause *SVG*, as far as I know, is still part of the *XML* namespace/pipeline, and announcing that anything *XML* is going to be deprecated and removed is concerning, imo.

I also think it's clear that developers knowing *XPath*, and its potentials, probably are not using it daily due its lack of improvements since 1999, so that asking *why*, *where*, or *what*, looks like a normal conversation to me, but "*dropping the bomb and the mic*" at the same time feels a bit "*off*", imho, but if there's anything I've said that made you put me in the "*folks that play word games*" category, I apology, 'cause even if I'm not sure where I gave you that feeling, it surely wasn't my intent.

- - -

I hope that the idea to improve *XPath* to let Web developers fulfill any requirement not satisfied by current *CSS* offer would be considered at least by other vendors, specially after reading that *XPath* has apparently security implications, while it's still a *W3C* recommendation ... it took much less to deprecate *SQLite*, and no security issue was obvious at that time, it's weird something known as insecure has been kept for 20 years in the platform and never got a chance to be updated.

-- 
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-707828597