I think this is mostly a result of the OOP ethos to think of actions on single objects, where each function call created a log message. This is then called in a

I think this is mostly a result of the OOP ethos to think of actions on single objects, where each function call created a log message. This is then called in a loop. Meanwhile the general case is actually that actions are performed on a collection of things, although this is often not obvious due to OOP design. But when working with collections it becomes obvious that log messages should be aggregates over collections ("2 out of items failed, errors: ..."). This then creates magnitudes less of logging. It's just not mainstream now.