Streamtoxication: How a Fluent API turns into a Tangled Mess
Speaker
About this talk
Should we use streams everywhere? Certainly, using streams is often clearer and more concise than iterating a collection. But sometimes stream code requires a complex combination of collectors, folding, monads, and nested flatMap operations, which makes the verdict debatable. In this session, we will pick several use cases, workout the best solutions in both imperative and functional styles, and then argue which is better. Of course, you'll get to vote! If you're a Java developer, you shouldn't miss this session! You'll have fun, replenish your energy, and leave with a better idea of where streams excel, and where you should stay with old-fashioned imperative style.
More talks to watch
Kotlin - the new and noteworthyAnton Arhipov
Dockerfiles, Jib ..., what's the best way to run your Java code in Containers?Matthias Haeussle
How to survive as a developer in the exponential age of AI - KeynoteSander Hoogendoorn
Your frontend is ☠️ ⚠️ Let's measure its impact with CO2 jsKo Turk
Test-Driven Design Insights - 10 Hints You Were MissingVictor Rentea
Let’s use IntelliJ as a game engine, just because we canAlexander Chatzizacharias