I don't have easy access to pypy so I can't run the benchmark on that I'm afraid. I'd love to see some relative results though. > You could argue anything that

I don't have easy access to pypy so I can't run the benchmark on that I'm afraid. I'd love to see some relative results though. > You could argue anything that’s performance bottlenecked shouldn’t be implemented in Python in the first place and therefore C compatibility is critical. Honestly, I think I'm heading towards "python should only be used for glue where performance does not matter". The sheer amount of time lost to waiting for slow runtimes is often brought up with node and electron, but I ran the benchmark in node and it's about halfway between go and python.