today i learned Chrome thinks React offers « flexible and powerful DOM manipulation »
https://developer.chrome.com/docs/web-platform/deprecating-xslt
how to demonstrate you don’t know what the DOM is without saying you don’t know what the DOM is
if they want to remove XSLT from browsers that is one thing, but you don’t have to pretend that you can somehow use React to replace all <i> tags in a document with <em> the way that
<template match="html:i">
<html:em>
<apply-templates select="@*|node()"/>
</html:em>
</template>
trivially can
@u2764 the raw DOM API wouldn't be too verbose to do the same thing anyway. why do the chrome devs think you’d want to use react fur this
@aescling i think anything that involves a TreeWalker is verbose
in this particular case you could get away with querySelectorAll or getElementsByTagName but that isn’t generalizable to an average XSLT transform
but this is an arbitrary example; the point is that React cannot do any DOM manipulation, including trivial
the chrome devs do not think you would want to use React for this; they do not see this as a legitimate usecase for web browsers. they believe that DOM documents should only ever be the outputs of functions, never the inputs
@aescling they are pretty explicit that sending XML over the wire is not “modern web development” and so should not be supported
@u2764 “not modern web development (derogatory)” is not exactly a meaningful criticism to me, is my point
@aescling unfortunately i don’t think the Chrome team knows or cares what is a meaningful criticism to you
@aescling yes, and?