The author expresses a dislike for benchmarking code in JavaScript due to the inherent complexities and challenges involved, such as the impact of the JIT compiler on accuracy. Different JavaScript engines like V8, JSC, and SpiderMonkey can significantly affect performance, leading to varying results during benchmarking. The author highlights the importance of testing code across different engines to ensure consistent performance. Solutions like using d8 on the server to control optimization levels and esvu with eshost-cli to manage engines are proposed. Benchmarking in browsers is more challenging, with limited control over the engine. The article concludes by acknowledging the difficulties of JavaScript benchmarking and the need for a simplified solution in the future.
https://byteofdev.com/posts/javascript-benchmarking-mess/