Hacker News Reader

Comment by rbranson | Hacker News Reader

As the saying goes: "that's awesome, if only it worked on IE6..."

If you care about IE6 these days, and aren't selling to corporate users forced to use it, then you're doing something wrong.

Also, you can just enable it when it's available, and fallback to comet etc when it's not.

While the numbers are falling, IE 6 users still account for a sizable percentage of the people that buy things from my site. Ignoring them would be "doing something wrong". Guess it just depends on what you're doing.

Also in case you are doing something that spreads virally, not supporting IE6 can change the viral loop from increasing to decreasing (you could lose 5% of invites/feed messages/emails/whatever depending on app).

I think the main issue here is not IE6 but all the modern browsers (FF 3.5, Safari 4, IE8) that do not support this feature. Targeting Chrome users only is not that appealing.

The feature was added to webkit so both safari, chrome and other will get the feature and so is firefox https://bugzilla.mozilla.org/show_bug.cgi?id=472529

This is HTML5, they will support it soon if not yet.

That's why you would use it where available, instead of targeting.

if (browser.supportsWebSocket) useWebSocket(); else useComet();

It really depends.

I recently did a bit of consulting work for a guy who has a large number of domains receiving primarily organic search traffic. Around 20% of the people hitting those (several million a month) are still using IE6.

You can use a Flash compatibility shim to make your sites use Web Sockets in some browsers and Flash sockets in others: http://github.com/gimite/web-socket-js

This is the best of both worlds; Flash works for IE users, and Web Sockets will hopefully be available soon in plenty of non-Flash browsers (like the iPhone).

Won't Chrome Frame fix the IE problem?

Reply on news.ycombinator.com