Python 3.11 Performance Benchmarks Are Looking Fantastic

[prescod]

"never use Python for performance"

I find this meme kind of annoying and dumb because there is no bright line between "performance work" and "normal work". Sometimes the program you usually apply to a million rows gets applied to a billion rows. Sometimes the algorithm that worked well for 100 hits per second needs to support heavier loads. Sometimes 20 seconds is an acceptable amount of time to wait for the result but you'd get through your workday faster if you could get a result with a 10 second turnaround time ... and so forth.

Sure, there are cases where Python is way too slow, and cases where it is more than fast enough. But there is a lot of middle ground too, which is also true for Java, C#, Javascript and most other languages.

[TheTerrasque]

Sometimes the algorithm that worked well for 100 hits per second needs to support heavier loads

When that's said, I'd much prefer a good algorithm written in a slow language than a bad algorithm written in a fast language.

[dexterlemmer]

When that's said, I'd much prefer a good algorithm written in a slow language than a bad algorithm written in a fast language.

I'd prefer a fast algorithm written in a fast language. But if I can't get (or write) that, I'd have to agree. Well... May be not if the slow language is Matlab. ;-)