simple-node-multiprocess

It’s not weird that you can’t share state between totally different processes except by passing in args. And you can make it thread-like if you prefer by creating a “load balancer” setup to begin with to keep them CPU bound. require('os').cpus().length Spawn a process for each CPU, bind data you need, and it can feel like multithreading from your perspective. More here https://github.com/bennyschmidt/simple-node-multiprocess

My bad it's on the insertion side, you can O(1) insert into the middle of Array-likes like Set in JS (which I use in this lib), where I think Python is O(n) for all it's Array-likes. Think you can O(1) append to an Array though. But there are at least a few other reasons Python is generally slower than JavaScript. It's popular in ML because it was popular in math, and it was popular in math because it's easy to teach in schools. People use Python for its ML libraries, and now its ML communities, not because it's a fast language - it isn't really. And has no browser implementation, so there are a few reasons I didn't choose Python. Reading it again I think I understand what the other poster meant now, but they also said "multi-process has nothing to do with the language" when it does have a lot to do with scaling Node especially to handle