what's funny is that the code compiles the small map-reduce and the for loop to exactly the same bytecode probably. :)
If not, then map / reduce offers non-trivial performance benefits over a for loop. Mapping, as far as I'm aware, is "embarrassingly parallel", assuming the function that's mapped is pure? I think?