function main(entrypoint) {
switch (entrypoint) {
default:
case 0:
// do some (...)
// now drop the thread and wait for input (external)
myInputFunc(function(result) { main(1, result); });
break;
case 1:
// return to here from input
var value = arguments[1];
// now do something with it ...
break;
}
}
function myInputFunc(callback) {
// in actuality this might be servicing a more complex UI
document.querySelector('#inputField').oninput =
function() { callback(this.value); };
}(Maybe requesting additional server data by what would be called padded JSON nowadays via a hidden frame, because no AJAX. And, maybe, we would have rather used global vars for control than anonymous functions, but this another story.)
:-)
Also, why not? Do you see any problem with that? As long as their numbers are limited, I don't see any problem?
The biggest difference is that JS is designed to run in an event loop inside a single thread. If you perform a 10 second blocking I/O your thread will freeze. You don't want your browser/tab to be unresponsive. Or in the case of a web server you want to accept incoming TCP connections as fast as you can.
You can achieve parallelism with threads but it's very tricky to scale. If you want a simpler, threaded, blocking programming model I suggest you take a look at Go.
Edit: Definitely read the original slides from Ryan Dahl's JSConf 2009 presentation, they perfectly explain the point of using JS: http://tinyclouds.org/jsconf.pdf
For all those Promises proponents out there ready to burn me down, this is how you do it in C:
And here the amazing Promises with await: Is it really that difficult to at least abstract this wait function away in the Javascript language?