Dear Ms @retoor, you claim to have demolished Rust but so far I have failed to observe any such claimed demolition event

With the newest patch these are the numbers

***benchmarking***
Time C: 0.1326432228088379
Time Rust: 0.1091299057006836
Time CPP: 0.47960424423217773
Time Borded CPP: 0.706519365310669
Time Jest Rust: 0.3468904495239258
***end benchmark***

Guess Rust is still on top :P

Dear Mr. 12 floating bitches,

please push the code. Also, you have to run it at least five times since they're so close these days.

Looking forward :P I have not much left :P

Let's see what the server of truth says: https://retoor.molodetz.nl/retoor/... :P

It's building, i'm crashing out of excitement.

@retoor It's still my newest code. I just pulled your latest commit and those are the numbers :P

@12bitfloat after one run, i see the server is failing, will repair that and we'll see :P

Repaired (I hope). Let's see. https://retoor.molodetz.nl/retoor/...

Fuck.

Fuck.

Oooeeeehh..

HOW DOES THE DUST TASTE?

```

Extracting books.

Extracted books.

***benchmarking***

Time C: 0.4344193935394287

Time Rust: 0.4379608631134033

Time CPP: 1.6448993682861328

Time Borded CPP: 2.1781139373779297

Time Jest Rust: 2.5989110469818115

***end benchmark***

```

@retoor How often did you have to run it to get that result? ;D

@retoor What CPU do you have btw?

@12bitfloat 3 times 😁 And I think i7-6700. On the street we call it the cpu of truth :)

It all just gets compiled to assembly. You can theoretically make any compiled language as fast as any other with enough mastery over the language.

@lungdart true, but there are some cpu optimizations regarding the compilers. This project for example, it really depends who executes it regarding who wins :P Every machine has different results! Only the Python version will always loose of course. But the python version is probably the most accurate one.

I kinda expect / hope that the C compiler is just the most sophisticated one and that'll make me win. I could also try clang instead of gcc ofc. My theory is that Rust must do some code hiding and do some unneeded stuff making it slower in the end.

@lungdart still using rantii / liked the last update (with previews and stuff?).

@retoor There is some overhead in Rust if you use a lot of the high level features, but if you know what you're doing it's not a big deal. And in the end it all gets optimized via LLVM, same as C via Clang ;P