It's Really Just That Bad

Zig only requires 75% of the text that Rust requires. Zig is faster to type and faster to say than Rust. Though way behind C, Rust comes out way ahead of Zig, alphabetically.

Worst news ever: the guy who made this benchmark impressed the csuite with the squiggly balls and promoted him to be your boss and supervise you rewriting your codebase from C to Fortran

"100 is one of the largest number known to man" Chat never disappoint

The funniest thing, I asked chatGPT to "create a levenshtein benchmark in fortran"... ChatGPT also had the 100 len limit. So it looks like the fortran code was largely a copy and paste job.

Casey's energy of borderline livid but not to the level of screaming, just to the level of "I need to explain every detail of why I'm angry with you" is how I feel at work trying to explain things to people.

The Fortran code had the right idea; you gotta wow them with your blazing speed and then tell them that comparison past the first 100 chars of the string is only available in the premium version

When I see a "graph" like that, I treat it like my unit tests. The tests are passing because the tests are wrong, not because the code is working :D

The Rust code similarly performs two heap allocations per distance calculation rather than using two pre-allocated arrays.

Casey: I'm mad because I have to do this for the second time. Me: Really looking forward for the third episode now LOL.

10:13 Compiler-explorer maintainer here, the colors are indeed random. Please note (1) we also have intra-line red highlights (hover over an assembly instruction to see), (2) the correspondence is made using debug info - so (at least for optimized builds) take it with a grain of salt.