I've weakly suggested this in the past (sorry, buried in old list
discussions and IRC), but I haven't come up with something that 1.
doesn't have nearly the overhead of web workers, and 2. doesn't have
nearly the footguns of C's direct thread-based model that's mostly
emulated by practically every remotely major software programming
language not using CSP or actors/processes. The first is difficult to
avoid without avoiding message passing altogether, hence why
`SharedArrayBuffer` appeared in the first place. The second is
difficult to avoid if you want to minimize message passing overhead,
especially without immutable objects (which can usually be sent
without copy between threads of the same parent process).
Given Erlang's parallel programming model has proven itself to stand
the test of time (it's hardly changed since the 80s) and that others
(such as Ruby and some Java circles) are planning to adapt it, I feel
it might be worth waiting for this stage-0 proposal to make it in in
some form or another first, *then* pushing for language-level support
of parallelism: https://github.com/rricard/proposal-const-value-types/
> Are there any threading proposals? If not, would anyone be interested in creating one?
> Webworkers are great, but require separate files that just aren't always convenient to maintain. I've
> created this wrapper for webworkers that allows users to create in-line disposable threads, somewhat
> similar to threads in Java.
> https://gist.github.com/Pamblam/683d5ae429448adfa6d6e7fb30de39b2 >
> If we could get something similar implemented natively that would be very cool.
> Robert "Gordie" Parham
> es-discuss mailing list
> [hidden email] > https://mail.mozilla.org/listinfo/es-discuss