4 ms·
For anyone familiar with the landscape: Are webworkers likely to improve dramatically as time goes on? For example, the cost of using web workers appears[1] to
by fizzbatter 10y ago
For anyone familiar with the landscape:
Are webworkers likely to improve dramatically as time goes on? For example, the cost of using web workers appears[1] to be far greater than just spinning up another thread in, say, Go[2]. I assume this is mainly due to how the browser is sandboxing JS. So, is there room for improvement here? Or have most things js related been so drastically optimized that we are without much hope here?
[1]: Purely speculative on my part.
[2]: Yes i know Go has green threads, it's purely an example. I was going to say Rust, but that seems like an unfair comparison.
- fenomas 10y agoIn my experience web workers aren't noticeably slower than regular JS (apart from the cost of copying any shared memory back and forth). They're slower in this demo (for some people but not others), but microbenchmarks in JS are very hard to to do right, and I don't think the author here was trying to make an accurate ubenchmark.