News for hackers. Stuff that matters.

A comment on A viable solution for Python concurrency. Parent comment

Re:A viable solution for Python concurrency by laurencerowe on Friday October 15, 2021 @03:46PM (#28882251)
Because JavaScript never had threads so I/O in JavaScript has always been non-blocking and the whole ecosystem surrounding it has grown up under that assumption.

JavaScript doesn't need a GIL because it doesn't really have threads. WebWorkers are more akin to multiprocessing than threads in Python. Objects cannot be shared directly across WebWorkers so transferring data comes with the expense of serializing/deserializing at the boundary.

[ Parent | on HN ]
Re:A viable solution for Python concurrency by catlifeonmars on Friday October 15, 2021 @03:53PM (#28882334)
JS now has shared array buffers.
[ Parent | on HN ]
Re:A viable solution for Python concurrency by laurencerowe on Friday October 15, 2021 @04:04PM (#28882487)
SharedArrayBuffer is just raw memory similar to using mmap from Python multiprocessing. The developer experience is very different to simply sharing objects across threads.
[ Parent | on HN ]