“Eight to four hours. Wow. The reason for that is that…” — Software Engineering Daily at 31:25
“Eight to four hours. Wow. The reason for that is that because measuring JavaScript code is tricky, we can't run a benchmark just once. We rely on an algorithm called new hypothesis, which tends to be the student test approach, which is we run each benchmark for each configuration 30 times before the change and 30…”
0:00
54:42