3 ms·
It looks more complicated. You get the same cumbersome communication primitive (channels), except now native code can easily get messed up. And it requires more
by H8crilA 3y ago
It looks more complicated. You get the same cumbersome communication primitive (channels), except now native code can easily get messed up. And it requires more care when developing the interpreter itself.
Using multiprocessing was actually pretty easy (apart from the communication primitives, which obviously suck).
- IshKebab 3y agoMultiprocessing means you need to deal with signals (which are ancient and powerful footguns), handle processes being killed, platform differences (fork vs spawn), etc. It really is a bad solution. Isolates are much much better. > You get the same cumbersome communication primitive (channels), except now native code can easily get messed up. I'm not sure what you mean by that. Native code has to be thread safe sure, but now it also can be thread safe! You can have native code that is actually properly multithreaded. A big win. > And it requires more care when developing the interpreter itself. Maybe. Not really an issue for the user though.