There's also no actual way of saying "no" to a web standard. The whole process is designed around moving a spec forward through stages. To quote Rich Harris, t

There's also no actual way of saying "no" to a web standard. The whole process is designed around moving a spec forward through stages. To quote Rich Harris, the author of Svelte: https://x.com/Rich_Harris/status/1841605646128460111 https://x.com/Rich_Harris/status/1841605646128460111 --- start quote --- saying 'no' is the key to good software design, but in standards you can only 'champion' proposals — you can't champion the _lack_ of a proposal. the best you can hope for is inertia. in my experience the only feedback that is welcome is around the details of an idea, never around whether the idea has merit in the first place, and you should expect to be reminded that implementers are the only people whose opinions actually matter. --- end quote --- and someone else in the same conversation: --- start quote --- You can't practically anti-champion standards that are small improvements to features that ought to have been abandoned, like Shadow DOM. Shadow DOM sucks, but it sucked a little less when they added CSS Module Scripts, Selection.getComposedRanges(), ElementInternals.shadowRoot… https://x.com/dfabu/status/1841936377350652391 https://x.com/dfabu/status/1841936377350652391 ---