Andy Wermke

Thanks for sharing the code! Definitely makes it easier. However, I don't see any obvious issue with it either. So if you are only running it in the browser (?),...

As long as threads.js run in the renderer process, it shouldn't make a difference.

@leopucci It should also work in the main process. It will then just use a different implementation (node.js instead of web implementation) internally.

Hey @ivan-aksamentov, that's so nice to hear! Always happy to help put technology to good use 🙂 Regarding the feature request… Good point. Didn't think that the pool on the...

@ivan-aksamentov I published the current state of the callback PR as `[email protected]` in case you want to try it. You can find some very basic documentation how to use it...

Sure. I think it should be feasible in userland. Haven't tried it yet, but in my head it looks something like this: ```js // worker.js import { expose, Pool }...

Hi @sebqq, generally speaking there is no real reason against it. The resulting code doesn't look too nice, though… We should rename some of them if we want to expose...

Hey @Comkiled. Very detailed description 👍 Bad news first: I don't use Windows, don't have an electron app using threads.js in the app thread at hand and thus I don't...

Great stuff! Thanks, @pkerpedjiev! Unfortunately I didn't find the time to review any earlier. Could you also provide a test case (we have a few tests that build using webpack...

Thanks for this massive contribution, @bebraw! I will have a more in-depth look tomorrow and will also try to explain a few things about the code (I know, it's pretty...