Hi, http://package.elm-lang.org/packages/elm-lang/core/4.0.5/Process looks really interesting but perhaps I don't fully understand it's intention.
The docs say: So even though JS runs within a single OS-level thread, Elm can still run > things concurrently but when I look at the code, it uses the Native scheduler which sticks things on a queue using setTimeout to put things on the end of the event loop but I was surprised to not see any Web Worker code or any issues relating to it? Process looks to be the perfect area for providing concurrency *and* parallelism through Web Workers either running stand-alone or talking to each other probably using promises to manage them? They are already libraries in this domain that provide thread pools as prior art. e.g. https://github.com/andywer/threadpool-js. Obviously this is just for front-end Elm rather than the nod to Node further down. What do you think? Thanks -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
