Evidently you haven't read or used WSGI, Tornado, or Twisted in any significant form. So Python sucks at multithreading, which doesn't mean that there aren't so

Evidently you haven't read or used WSGI, Tornado, or Twisted in any significant form. So Python sucks at multithreading, which doesn't mean that there aren't some very good workarounds, and that multiprocessing works as good as any other place. Btw, if you HAD tried to use Python on any significant way, you would have known that WSGI on Apache recycles the VM for multiple requests, which is the reason why it's suggested to do static file serving outside of Apache within the same server. And, oh yeah, I have yet to hear from anyone except people doing CPU-intensive processing have the programming language be the bottleneck. Congratulations if your system is CPU or network-limited, in which case I'd hope that you're writing something in a lower-level language to handle the situation, but in 99% of large site installations, even if you cache all your IO, it's still going to be the big bottleneck of your system. Seriously, opening a remote socket and sending shit through it is almost always a bigger issue than pushing HTML. Finally, it still doesn't change the fact that some of the biggest web sites are running Python in the back end and they couldn't be happier.