I am not exactly sure why multi-threading support in JavaScript has been avoided, even though there is a strong case for real multi-threading support in JavaScript. This is usually reflected in the race to fit every event callback within 16ms to avoid dropping frames.
To cover for some of these deficiencies, web workers, worker_threads, process.fork, etc have been introduced in the past, all of which are cumbersome to use. I understand that multi-threading is difficult to get right, and it provides a number of challenges including making it easy to create difficult-to-debug bugs, but I am of the opinion that we can at least start a discussion on this. In light of this, I created a draft of what I think is a "safe" way to add "user-space", first-class multi-threading support in JavaScript. The link to the gist: https://gist.github.com/xkizer/d63ac72ef48720c2066fbc9d3580ea90 A few things to note: 1. I am not an expert in multi-threading, and could have made some otherwise obvious wrong assumptions/blunders 2. I am not an expert in JS engines, and do not know how easy/difficult these are to actually bring to fruition I am looking for comments and constructive criticisms. Thanks in advance. -- Kizer
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
