undefined | Better HN

0 pointsaroch11y ago0 comments

Or a great choice if you want to shoehorn your wished spec into reality?

0 comments

3 comments · 1 top-level

pluma11y ago· 2 in thread

Maybe the W3C didn't want a repeat of what happened with XHTML2.

arochOP11y ago

If memory serves there were a number of issues with XHTML2, chief among them being it didn't serve the original intent of XHTML very well. HTTP/2 has good meaning but some of the deign choices were made because Google wanted them not because they were necessarily best (at least from my understanding as an interested spectator).

pas11y ago

Could you expand on that? Is there a list of these features, or at least a blogpost that interested parties could read to quickly get up to speed with the special interest influences currently observable in the spec?

1 more reply

j / k navigate · click thread line to collapse