Well, all those points were discussed and there are sound reasons why they are as they are in HTML5
Versioning — it just does not make any sense. Browsers render web content to their abilities, not by spec. Some my not support parts of HTML4 but support other parts from HTML five.
No doctype — creators of HTML5 would be glad to get rid of it, alas, it is required to force browsers to use standards compliant rendering mode. Without doctype they fall back to quirks mode, which is bad.
CSS — unified rendering would be nice, but that's not the subject of HTML spec. And reset stylesheets are just plain stupid.
Self closing <script> — historical reasons… :)
Custom tags — what? You can invent any tags you like and modern browsers will allow you to style them. If you want custom tags, you don't need a spec. The point of the spec to define agreement on what which elements means.
Custom attributes: HTML5 has that in the form of data-* attributes and elements get element.dataset accessor.
Versioning — it just does not make any sense. Browsers render web content to their abilities, not by spec. Some my not support parts of HTML4 but support other parts from HTML five.
No doctype — creators of HTML5 would be glad to get rid of it, alas, it is required to force browsers to use standards compliant rendering mode. Without doctype they fall back to quirks mode, which is bad.
CSS — unified rendering would be nice, but that's not the subject of HTML spec. And reset stylesheets are just plain stupid.
Self closing <script> — historical reasons… :)
Custom tags — what? You can invent any tags you like and modern browsers will allow you to style them. If you want custom tags, you don't need a spec. The point of the spec to define agreement on what which elements means.
Custom attributes: HTML5 has that in the form of data-* attributes and elements get element.dataset accessor.