I can't even begin to explain how wrong this benchmark and the author's conclusion is. I'd rather see a benchmark of apache vs a fibonacci function than read this nonsense.
This is a banal point. Yes, separate compilation hurts performance. But that's what link-time optimization is for. GCC and LLVM alike can both do link-time optimization.<p>You might as well say "gcc with -O0 is slower than V8, therefore V8 is faster than gcc".
Obscure? It's interesting but I can't see a case where I'd be recompiling C code every time I want to run something. On the other hand, we can't just go AOT compile using V8 (AFAIK) so let's call V8 always slower?
In my mind, the value of this benchmark isn't to prove that V8 is absolutely faster than C but that there is intrinsic value in doing runtime compilation instead of / on top of compile-time optimizations.<p>It's a demonstration of <i>why</i> run time optimizing compilers/runtimes may one day become faster than compile time optimizing compilers.
Every reader of that blogpost: Oh blabla unfair, the C code of the thing would be faster if the thing had included the other thing blabla.<p>I think its a fun benchmark :)