> If Chrome’s implementation of web workers is too heavyweight, that’s Chrome’s problem.
You absolutely have a point. Ben Kelly from Mozilla pointed out to use that their workers are _much_ cheaper than ours. We apparently never invested much time in optimizing Workers as they are rarely used.