3 ms·
JS doesn't really support threads so that's probably a big part of it. Traditionally JS applications have never been very "heavy" so it's never been a problem
by jiggy2011 15y ago
JS doesn't really support threads so that's probably a big part of it.
Traditionally JS applications have never been very "heavy" so it's never been a problem as you could just use the other cores to run JS for other browser tabs etc.
Of course now both cores and JS usage are increasing so this will have to change.
- miohtama 15y agoJavascript supports web workers which are effectively threads with the exception they don't share the application memory, but communicate over postMessage(). This makes possible share the calculations across the cores, but since postMessage() serializes each transferred object the effectiveness of this might not be that good.
- jiggy2011 15y agoyes, that's not really going to work for something that needs good latency like a physics engine.
- deleted 15y ago[deleted]