Hacker News Reader

Given microsoft's history of browser releases, I'd prefer an out-of-date implementation that js libraries can wrap to a wait-and-see approach. It would be better than nothing -- websockets solve an important and annoying problem.

So you want another IE6? That's why we were stuck with an incorrect box model implementation. When they implementation that standard before it was finalized, we got years of broken layouts.

The latest nightlies conform to the latest draft. And Safari 5 supports WebSockets.

But yes, it's an annoyingly volatile standard-in-progress.

Safari 5 supports WebSockets, and supposedly the nightly builds of Firefox do as well.