why Javascript SetTimeout() is not multithreaded

Question

I have a test:

Html:

<div id="f1">Empty</div>
<div id="f2">Empty</div>

?

js:

var s1 = function() {
? ??for (i = 1; i < 1000000000; i++) {
? ? ? ??var b = i * i;
? ??}
? ??$('#f1').html('Set');
}

var s2 = function() {
? ??if ($('#f1').html() == 'Empty') {
? ? ? ??$('#f2').html('Multi Thread');
? ? ? ??return;? ? ? ? ? ??
? ??};
? ??$('#f2').html('One Thread');
}

setTimeout(s2,110);
setTimeout(s1,100);?

is there any real reason why setTimeOut() not run in different threads, instead like event model ?

jsfiddle

Answer 1

Javascript is not multithreaded nor non-multithreaded per se. However, the specific implementations of Javascript that currently are implemented in major browsers mostly ARE single-threaded.

In addition, for proper multithreading, the language needs to have facilities for shared memory, locks, semaphors and other concurrent programming tools, which JavaScript as is currently defined does not have (for example, there is no way to describe how concurrent JS threads would control who gets to update DOM objects that are of course, shared since there's only one DOM in a window).

There are attempts to make JS more parallelized - look at web workers, Intel's River Trail, Google's HTML5 work and more.