> evaluation begins only when a terminal operation is invoked. In this example, line (1) creates a stream, but does not evaluate it, line (2) sets up an intermediate filter operation but still does not evaluate the stream, and finally the terminal collect operation on line (3) evaluates the entire stream pipeline.

It's quite clear, reading beyond just the code, that the original author is talking about _computational_ efficiency.

It feels like you missed the point — that streams are only evaluated lazily as needed — in order to poke fun at the (toy) example.

The Java code can (and in a real-world application would), be made more consise (e.g. via static imports) but the author is deliberately being more verbose to be more explicit in what's going on.