We do have very harsh sanitation and validation on LFGSS. It's also a text-based internet forum. We do not need canvas or most of the other new tags.
Your statement is true only if you think that what is currently LFGSS is all it need be. I happen not to believe that, and I do want the newer features when they are available and will be using them when they're widely adopted. You say there is no need for canvas but a skid patch calculator would be much nicer if we had canvas, as would a polo knockout tournament graph or a bike size diagram. Just because we don't have those things doesn't mean you shouldn't dream of having them.
My choice: drag heels in favour of existing support and be constrained by the past or push at the edges to help drive support and allow myself to dream of the future.
I'm choosing the latter.
Besides, most of HTML5 is a small-step improvement over HTML4. The tags make sense, and existing browsers won't treat things like as tag soup if you use CSS to declare footer as a block element with the spacing and font desired.
Using most of the commonly agreed upon (and unlikely to change) parts of HTML5 will result in semantic and cleaner code. That is the point... less code, clearer code, and ultimately from that code that is parsed and rendered faster.
Your statement is true only if you think that what is currently LFGSS is all it need be. I happen not to believe that, and I do want the newer features when they are available and will be using them when they're widely adopted. You say there is no need for canvas but a skid patch calculator would be much nicer if we had canvas, as would a polo knockout tournament graph or a bike size diagram. Just because we don't have those things doesn't mean you shouldn't dream of having them.
My choice: drag heels in favour of existing support and be constrained by the past or push at the edges to help drive support and allow myself to dream of the future.
I'm choosing the latter.
Besides, most of HTML5 is a small-step improvement over HTML4. The tags make sense, and existing browsers won't treat things like as tag soup if you use CSS to declare footer as a block element with the spacing and font desired.
Using most of the commonly agreed upon (and unlikely to change) parts of HTML5 will result in semantic and cleaner code. That is the point... less code, clearer code, and ultimately from that code that is parsed and rendered faster.