6 ms·
If Chrome’s implementation of web workers is too heavyweight, that’s Chrome’s problem. I don’t think there’s anything in the existing spec that makes it inhere
by iainmerrick 9y ago
If Chrome’s implementation of web workers is too heavyweight, that’s Chrome’s problem.
I don’t think there’s anything in the existing spec that makes it inherently heavyweight (or if there is, this new proposal doesn’t explain the problem).
Current standards shouldn’t be thrown out and rewritten on a whim. All else being equal, current standards should be supported forever.
If you still really really want to rewrite some bit of HTML5 from scratch, start with Web Audio.
- dassurma 9y ago> 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.