undefined | Better HN

0 pointsDalewyn2y ago0 comments

No, backwards compatibility is the responsibility of the browser, a la quirks mode[1][2] in ye olde days.

HTML6 or CSS4 could have a fresh, clean start and there's nothing preventing that.

[1]: https://en.wikipedia.org/wiki/Quirks_mode

[2]: https://www.quirksmode.org/css/quirksmode.html

0 comments

What's preventing that is the large installed base of sites on the 'net. Quite possibly, the majority of web content has already been created (1), and it's getting worse as old sites are shut down.

Also, Safari is a thing (and personally I prefer FF for webdev, though Moz is certainly working hard to turn me away).

(1) those worth reading anyway, rather than generated content

madeofpalk2y ago

What would be the point of that if no browser would support it?

DalewynOP2y ago

I'm not sure what you're getting at?

The browser landscape today is composed of practically just one browser: Chrome. It is easier than ever to get browsers (read: Chrome) to implement different rendering schemes based on identifiers or descriptors provided by web devs.

Supporting the latest and greatest is a great marketing ploy, browsers (read: Chrome) are incentivized to support them. Browsers that don't will be forced to support them lest they become even further irrelevant.

Quirks Mode happened, Quirks Mode V2 can happen.

madeofpalk2y ago

I think it is a very bad idea for a single browser vendor to deliberately subvert standards process and attempt to steamroll the web with their own proprietary tech!

1 more reply

j / k navigate · click thread line to collapse

0 comments

tannhaeuser2y ago

What's preventing that is the large installed base of sites on the 'net. Quite possibly, the majority of web content has already been created (1), and it's getting worse as old sites are shut down.

Also, Safari is a thing (and personally I prefer FF for webdev, though Moz is certainly working hard to turn me away).

(1) those worth reading anyway, rather than generated content

madeofpalk2y ago

What would be the point of that if no browser would support it?

DalewynOP2y ago

I'm not sure what you're getting at?

Quirks Mode happened, Quirks Mode V2 can happen.

madeofpalk2y ago

I think it is a very bad idea for a single browser vendor to deliberately subvert standards process and attempt to steamroll the web with their own proprietary tech!

1 more reply

j / k navigate · click thread line to collapse

0 pointsDalewyn2y ago0 comments

No, backwards compatibility is the responsibility of the browser, a la quirks mode[1][2] in ye olde days.

HTML6 or CSS4 could have a fresh, clean start and there's nothing preventing that.

[1]: https://en.wikipedia.org/wiki/Quirks_mode

[2]: https://www.quirksmode.org/css/quirksmode.html