Web workers and web sockets are, IMO, the two most interesting changes/additions to the JS/html landscape in a while. (Canvas probably being a close 3rd...)
Unlike web sockets, though, web workers don't seem to have been given as much love - there aren't a ton of cool demos, there don't seem to be any abstraction libs (i.e. socket.io), etc.
Are web workers still too immature/unsupported? Is an abstraction library (I'm thinking thread-pool style libs available in other langs, or maybe even some sort of actor model for passing data across workers) unnecessary?
At any rate, glad to see a book out on the subject!
I agree Andrew...
It would be great to see more:
* Libraries that making the developer life easier.
* Cool demo to what can be done with web workers today and transferrable objects.
My little contribution is with this set of examples (from the book) - http://greenido.github.com/Web-Workers-Examples-/
As for "Are web workers still too immature/unsupported?"
I would say that our current state is much better and in the near future all the major browsers will have them: http://caniuse.com/#feat=webworkers