Comments by "Mikko Rantalainen" (@MikkoRantalainen) on "It's Really Just That Bad" video.

It's pretty obvious that whoever did this benchmark didn't bother to write the best code for each language. PHP has a function called levenshtein() in the default install which is implemented in C. Should be pretty fast, right? If you re-implement that poorly in PHP, obviously the performance is going to suck.
5
9:52 The colors are used to express that a single line of code can be split over multiple locations in assembly. For example, the for() statement in C code is split on lines 95,96,114,115,116 and all these lines have identical color to make it easier to notice this. The colors appear purely random so green doesn't mean something else than red.
2
Why bother poorly authored "language benchmark" when project called The Computer Language Benchmarks Game is already available and has about decades to improvements to implementation of each variant of the program. If somebody can figure out how to make language X faster for the task in benchmark, that version will replace the old benchmark version.
1
@dmitripogosian5084 My point was that if you intentionally use suboptimal code for a given language, it's not a fair test.
1
@dmitripogosian5084 When you use malloc() in C, it's not implemented in C but uses a syscall to request the operating system to do the heavy lifting. Do you think that malloc() shouldn't be used in C either? The function levenshtein() is a standard PHP function so if you decide to now use that you're simply intentionally writing inferior code. I guess you could also interpret this as "it's stupid to create benchmark using so simple algorithms that the algorithm could be part of the language spec for some language". That is, unless the whole intent is code golf and you want to show superiority of language such as GolfScript.
1