Live data from Hacker News

Make Your UI More Responsive with HTML5 Web Workers

storminthecastle.com

1–10 of 17 posts

Re: Make Your UI More Responsive with HTML5 Web Workers

#4
post #2

Unfortunately they're not supported in IE9 or below, which this article oddly fails to mention. So a more accurate title might be "make your UI more responsive for ~60% of your users with HTML5 web workers".

I think this is the case for nearly every technology, new, or old, and although they wouldn't be amiss to mention it, 60% is a lot better than a lot of other techniques which get mentioned here.

Re: Make Your UI More Responsive with HTML5 Web Workers

#7
post #2

Unfortunately they're not supported in IE9 or below, which this article oddly fails to mention. So a more accurate title might be "make your UI more responsive for ~60% of your users with HTML5 web workers".

Sadly, can't even use it for cross-platform packaged apps (min requirement: chromium, iOS browser, android browser) because the android removed support after 2.1.

Re: Make Your UI More Responsive with HTML5 Web Workers

#8
post #2

Unfortunately they're not supported in IE9 or below, which this article oddly fails to mention. So a more accurate title might be "make your UI more responsive for ~60% of your users with HTML5 web workers".

I think this is the case for nearly every technology, new, or old, and although they wouldn't be amiss to mention it, 60% is a lot better than a lot of other techniques which get mentioned here.

Oh, absolutely. Web workers are awesome and hopefully the future, but it seems a bit disingenuous not to mention the huge caveat that currently prevents their being adopted in a more widespread way.

Re: Make Your UI More Responsive with HTML5 Web Workers

#9

Step 1. Make your server more responsive.

I realise this is snark about the article going down, but it's actually a good point too. Not much point in optimising the client side if all your dynamic requests take a second for the server to process.

Re: Make Your UI More Responsive with HTML5 Web Workers

#10
post #9

Step 1. Make your server more responsive.

I realise this is snark about the article going down, but it's actually a good point too. Not much point in optimising the client side if all your dynamic requests take a second for the server to process.

Good point. I once spent three months developing a highly optimized dynamically loading Google Maps point & line overlay library capable of smoothly scrolling through thousands of elements with hundreds on screen on 10 year old single-core Pentiums.

In the end the server team ended up implementing a home-grown geo-search on an XML document store with an average query time of several seconds.

Post reply on HN