4 ms·
Reminder that the Computer Languages Benchmark Game itself recommends against using it to draw general conclusions about performance of languages in real-world
by valw 5y ago
Reminder that the Computer Languages Benchmark Game itself recommends against using it to draw general conclusions about performance of languages in real-world apps: https://benchmarksgame-team.pages.debian.net/benchmarksgame/why-measure-toy-benchmark-programs.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
> We are profoundly uninterested in claims that these measurements, of a few tiny programs, somehow define the relative performance of programming languages aka Which programming language is fastest?
Now, I challenge you to find a major bloated software where the main source of overhead is Python interpretation. IME it's always something else, like the surrounding UI framework.
The Office suite is written in C++ and is badly bloated, obviously not because of language execution overhead but because of technical debt, which if that's any indication recommends against using low-level languages.
- teakettle42 5y ago> I challenge you to find a major bloated software where the main source of overhead is Python interpretation In every piece of non-trivial software I’ve written in python, the main source of overhead has been Python interpretation. I don’t think it’d be hard at all to meet your challenge.
- igouy 5y agoIf it wouldn't be hard at all, we're left to wonder that you don't seem to have tried.
- teakettle42 5y agoPerforming a legitimate performance benchmark of even one piece of enterprise Python software — much less across a representative survey — is well beyond the reasonable scope of a comment board reply.
- igouy 5y agoSo, too hard.