Me when I found out for() is 5-6 times more efficient that .forEach

If you're in a compiled language, that's a compiler bug (g++ will generate the same assembly for both), if you're in an interpreted language... Well, don't worry about speed...

For() might be faster.

But

foreach(){
foreach(){
foreach(){
}
}
}

Is soooooo much easier to read 🤪

Looping and incrementing a register is faster than loading an object reference out of a struct array and incrementing a pointer by the struct size? Whoda thunk

too bad if you use elixir tho

Laughs in C

Gimme numbers and tell me that any user will notice this.

I will find a lot of other numbers the user will notice a lot more. :)

Microoptimization - if unnecessary - is really just a shiny way to screw yourself over and over for nuts.

@IntrusionCM with animation work it's definitely noticeable

Worrying about that kind of stuff in JS is kinda funny. Even in the fastest compiled language I wouldn‘t care unless it‘s a really huge amount of iterations.

@Lensflare like I said with animation it really is noticeable

@lopu yeah. It’s still only a constant/linear factor. Optimizing it is kinda pointless. Because on a different machine/browser it can still be too slow to be acceptable.

Optimizing whats going on in each iteration will be better, but still linear.

The real solution is bringing down the iteration count. I don’t know the context of what you are using the loop for, but on other platforms there are mechanisms like lazy lists in UI which are solutions for that problem.