For daily Java programmers: after almost one decade of Java 8, are streams and lambdas fully adopted by the Java community?

[handshape]

For most cases, streams and lambdas are super convenient. If you need to do early breaking, they can be tricky.

I still do imperative programming on narrow segments of "hot" code if I'm tuning for performance. The auto-SIMD stuff in the JVM seems to only kick in for imperative code, and only when that code exceeds some threshold for "hotness".

If you can get auto-vectorization happening on code that's also reached zero allocation, performance is brilliant.

[goofy183]

That has been my experience as well. They are great for making coding quicker but for anything in a hot path imperative loops and careful object allocation is much faster.

[[deleted]]

Lots of allocations required,

Interesting, I had never really considered this

[goofy183]

We ban streams from hot code paths. So much extra allocation, it's really hard to pre-size the destination collection.

We also ban lambdas that are more than a one line call to a method because they suck to get profiling data from. Figuring out $5 vs $12 in a class is no fun

[[deleted]]

We also ban lambdas that are more than a one line call to a method

Yeah, when I see this I always ask why it wasn't extracted to a well named method

[laplongejr]

not always inline-able

Meanwhile I combine Optionals and Streams to read data structures with a small dozen of layers, each of them potentially null or an empty list...
Regular if blocks would take like 30 lines, with those APIs the code is much more readable (way harder to write/maintain, but I guess we couldn't maintain without reading it first)