4 ms·
The entire exercise is an attempt to compare apples to apples. In your example, both the C bin and Rust bin are using X, GPU, etcetc - so they warrant no disti
by adkadskhj 6y ago
The entire exercise is an attempt to compare apples to apples.
In your example, both the C bin and Rust bin are using X, GPU, etcetc - so they warrant no distinction. So what is different? What is included in the Rust binary that isn't in the C? Because that's what is being tested in these types of comparisons.
This difference may be because some language included inefficient instructions - has bloated includes, etc. Or it could be because you're comparing Apples to Oranges, eg one ships with libc in the binary, and one dynamically links to it.
- colejohnson66 6y agoI’m not attempting to compare apples and oranges. I’m ranting about how almost every time someone posts something about tiny programs (like 100 line JS programs or wherever), someone has to chime in about how they’re able to do something so small because they’re using all these abstractions (code) below them and, as such, it’s not an achievement. Again: it was just a rant.
- adkadskhj 6y agoSpecifically that your rant is here because the Parent comment mentioned Libc - but this is because the Rust version isn't using that - but the C lib is. So it's Apples to Oranges because they're fundamentally doing different things, and yet we're comparing their Line Count. That's not only reasonable, it's necessary if you want an Apples to Apples comparison. That's why we're not concerned about the code to render with GPU or some other junk - but we are fundamentally talking about two programs that do different things - but then comparing their line count. Your rant may be valid in other cases, but it seems super off base here. Your rant has, imo, nothing to do with what's happening in people pointing out the discrepancy.