Interesting that everything except "map" is so close as to be spitting distance, meaning in a modern engine it doesn't matter.

But that makes me question the testing methodology too... though I have to keep reminding myself that what holds true in compiled languages and assembler oft have nothing to do with interpreted languages like JS, where it comes down not to the number of ML level steps it takes to do things, but where the creators of the interpreter put their optimization choices.

Though I see this test too does the re-re half-tweet garbage "else after return".

Is there some book, tutorial, style guide, or pedantic half-tweet linter out there actively encouraging said coding behavior because I've seen it in several dozen "new" codebases the past year...

Or are we just looking at more ignorance, incompetence, and ineptitude?