Viewing profile — 8NNTt8z3QvLT8tp

It's not pearl clutching to suggest that websites will build around quirks of a specific model and then we'll be stuck with it forever. This is an issue for future Google as much a…

There's something to be said for the security benefits of not having a JIT though. Especially if you've used Rust for the engine you should have pretty solid security.

https://github.com/mfreed7/xslt_polyfill/pull/5 - it will be able to do this soon.

https://github.com/mfreed7/xslt_polyfill/pull/5 - someone's made a PR that looks like it would allow Mason's polyfill to work directly from the XML file.

Someone's already added a PR to allow exactly that. You just include a script tag within your XML file.

Another big example is mutation events which are gone across the board now.

Why is it better to drop users onto the RSS page and say copy the URL in the address bar, rather than just giving a copy button that puts it on the clipboard and say put this in yo…

You've completely disregarded the other examples of breaking changes that have already been made. The open web still survives afterwards. The web isn't immutable no matter how much…

Fwiw the meetings aren't closed, unlike w3c the whatwg doesn't require paid membership to attend. The bug trackers are also a fine place to provide community feedback. For example …

Thing is the new APIs added to the web are generally quite well specified with quite good tests. These older legacy APIs sometimes don't even have a standard and almost definitely …

Mutation Events were once in all 3 moderns engines plus some legacy ones and is now removed from everything. Third-party cookies are now heavily restricted and while not quite remo…