I think the HTML5 project is misguided in the same way that ES4 was. It is trying to do too much without a clear mission that defines the problems it is solving. I think the project needs a reset. I want to refocus it with the intention of producing the smallest possible standard, rather than the largest possible standard.
I would call the replacement project HTML4.2. It would be tempting to call it HTML4.1, but the current HTML standard is HTML 4.01, so the potential for confusion is too great.
Opinionated Doug is opinionated, and I think it's a good thing.
This specification normatively defines the fifth major version of the HTML vocabulary. It provides the details necessary for producers of HTML content to create conformant documents. By design, it does not define related APIs nor attempt to specify how consumers of HTML content are meant to process documents.
a version more usable to help you actually writing HTML5
Comet doesn’t have to be a hack. Currently, as we saw last time, Comet relies on undocumented loopholes and workarounds, each one with some drawbacks. We can make Comet work effectively in every browser, using streaming transports on subdomains of the same second-level domain, or using script tag long polling across domains. But this leaves Comet developers implementing (and more frustratingly, debugging) several transports across several browsers. Traps are numerous and easy to stumble into.
event-source is the future of all Comet things.