3 ms·
In theory this is an awesome idea, but it faulters for a couple reasons imo. One is graceful degradation, in case of bugs in a browser, or a browser doesn't sup
by jchw 9y ago
In theory this is an awesome idea, but it faulters for a couple reasons imo. One is graceful degradation, in case of bugs in a browser, or a browser doesn't support new syntax, etc.
If the spec had byte-for-byte specification for what happened when, this would be fine, and of course that is the case for say, JSON, which has remained roughly the same since inception. But given how fast CSS and JS are moving, it would be painful to do this same thing with either of those.
XHTML did this with HTML, but it kind of sucked because some browsers would reject what others would accept in some edge cases, and that is terrible. Plus, there's already a lot of bad HTML in the wild and XHTML casted some doubt on our ability to maintain a major HTML compatibility break.
- deleted 9y ago[deleted]
- Sohcahtoa82 9y ago> or a browser doesn't support new syntax, Then the user needs to update their browser. It's pretty inexcusable these days to not keep your browser up-to-date, and browsers tend to support new language specs before those specs get widespread usage.
- vacri 9y ago> before those specs get widespread usage. 'widespread' This would kill off new features, basically. No-one would implement a new feature, because it would kill off their users in $other_browsers completely, and browsers add new features piecemeal - without seeing which features are popular, there's no way to tell what is best bang-for-buck to work on.