> So why not Because multithreading introduces a lot of complexity, making it inflexible and hard to scale. Of course you would never do it if the code was fas

> So why not Because multithreading introduces a lot of complexity, making it inflexible and hard to scale. Of course you would never do it if the code was fast enough to not have to. I never had to consider it, I could generate about 16 complete flow fields per frame on a 512x512 map with no quadtree optimization. It sounds like a nice way to learn webworkers, but I think you're always better off hitting the perf bottleneck first, rather than trying to design around it early.