@dexter Perl as the highest sounds pretty weird given how inefficient Python is in comparison, and pretty sure Lua has among the lowest impacts. Go and Java in the first part also seems kind of weird. Really wonder how they came up with those numbers, specially given how different all those languages are.
@dexter Plus kind of gives score-vibes instead of like, how efficient each language are for their tasks, things like networking, decoding/encoding, high-activity daemon, low-activity daemon, throwaway utility (like most unix commands), …
@GuillaumeRossolini Yeah, I think a better one would be to analyze (rather than score) the standard/extended-standard library where quite a lot of languages ship cryptographic algorithms, json/xml encoders/decoders, http client/server library, … And I guess measuring the CPU time + memory usage of runtimes for initial launch, threads, `fork()`, idle/sleep, …
@lanodan yep, this looked like some interesting problems to determine the capabilities of a language, gauge how fit each is as a general purpose tool, identify possible shortcomings
But actual applications in the wild don’t necessarily implement these edge cases often (or ever), and that’s perhaps what that warning was about
If you’re going to benchmark, at least share your versions and settings so that they are readily available to readers. And if you write an article covering the research, do the same?
@GuillaumeRossolini Well changing the settings would be appropriate for knowing how to tune the operating system, which is all too often non-existant or lacking in official documentation.
> community reviewed best settings
Well for libre systems (which is what fefe used) that quite ought to be the default one.