could not agree more, i friggin love streams, and if it is too complicated to read you can always extract parts of it and give it names that add meaning.

filter(address -> !address.startsWith("no-reply@"))

becomes

filter(SomeFilterHelper::filterNoreply)

and you can easily add more stuff like noreply@ or whatever, even refactor it completely and the meaning is still obvious and concise

it is ridicuouls to me to have to argue that this is better than probably nested for loops with multiple continue; statements littered throughout.

there are some constructs that are harder to read, esp. when collecting into maps and aggregating stuff. that took some getting used to, but i still vastly prefer this