[dmitriid]

> The standards are backwards compatible and evergreen.

They are definitely not backwards compatible. Most of the modern web will be broken on older devices. A few of the newer standards couldn't even be properly polyfilled on some older browsers.

And some of them are definitely not evergreen. Marquee is the one that will definitely spring to mind. But then there was Custom Elements V0 that Youtube was rebuilt in and removed when Youtube was rebuilt in V1. And then there's the push by browsers to remove alert/prompt/confirm.

> Your walled garden withers.

These "walled gardens" use the platform as much as your half-baked lib/framework you inevitably end up with. Because there's nothing else to use in the browser but the platform.

And the platform sucks. It offers almost zero functionality for anything beyond a static text page with a few images on it

[LtWorf]

> Most of the modern web will be broken on older devices.

And the super heavy js websites will work?

[dmitriid]

Not necessarily.

How old and how backward compatible are you thinking?

- Symbol is 2014-2015

- Map is 2014-2015

- Weak* data structures and their methods span 2014-2021

- WebGL 2.0 is 2017-2021

- Custom Elements are 2017-2021

- Chrome-only non-standards (hardware APIs and a bunch of others) are pumped out at a rate of up to 400 per year

- WebAssembly MVP is 2017-2018

And so on. That's off the top of my head. None of them are backwards compatible. Some of them cannot be polyfilled.