> The negatives are often theoretical They are not theoretical. Too bad webapicontroversy.com has been shut down (it looked like this [1]), but you can scroll

> The negatives are often theoretical They are not theoretical. Too bad webapicontroversy.com has been shut down (it looked like this [1]), but you can scroll down to "defer" and "considered harmful" in Mozilla's positions here: [2] There are more, of course, but they are not visible unless you're willing to follow thousands of issues across hundreds of GitHub repositories. One that springs to mind is, of course Constructible Stylesheets. Mozilla and Safari: the spec describes an algorithm that leads to deadlock in trivial code, we wont implement it until this is fixed. [3] Chrome: ship it, because lit-html (developed by Google) wants it and is already using it. And then procedes to gaslight people and misrepresent their positions (cant' find the relevant link, but at this point I can't find the will to dive into the cesspool). [1] https://user-images.githubusercontent.com/32768/108985355-3f580280-7691-11eb-8894-b450270a8410.png https://user-images.githubusercontent.com/32768/108985355-3f... [2] https://mozilla.github.io/standards-positions/ https://mozilla.github.io/standards-positions/ [3] https://github.com/WICG/construct-stylesheets/issues/45#issuecomment-521096423 https://github.com/WICG/construct-stylesheets/issues/45#issu...