Explore >> Select a destination
|
You are here 
|
www.jrebel.com | ||
| | | | |
www.chrisritchie.org
|
|
| | | | | Doing distributed processing with Java's parallelStream. | |
| | | | |
winterbe.com
|
|
| | | | | Learn Java 8 streams by example: functional programming with filter, map, flatMap, reduce, collect, lambdas, sequential and parallel streams are covered in-depth in this tutorial. | |
| | | | |
nikgrozev.com
|
|
| | | | | Oracle has recently released a 3-week JDK 8 Massive Open and Online Course called "Lambdas and Streams", which discusses the new JDK8 functional features in ... | |
| | | | |
richardstartin.github.io
|
|
| | | The streams API has been around for a while now, and I'm a big fan of it. It allows for a clean declarative programming style, which permits various optimisations to occur, and keeps the pastafarians at bay. I also think the Stream is the perfect abstraction for data interchange across API boundaries. This is partly because a Stream is lazy, meaning you don't need to pay for consumption until you actually need to, and partly because a Stream can only be used once and there can be no ambiguity about ownership. If you supply a Stream to an API, you must expect that it has been used and so must discard it. This almost entirely eradicates defensive copies and can mean that no intermediate data structures need ever exist. Despite my enthusiasm for this abstractio... | ||
