3 ms·
The fact Java 8 streams only address a tiny sliver of the concurrency problems addressed by JCIP. In practice, Java 8 parallel streams are generally discourage
by cle 9y ago
The fact Java 8 streams only address a tiny sliver of the concurrency problems addressed by JCIP.
In practice, Java 8 parallel streams are generally discouraged outside of raw number crunching, which is rarely where we need parallel speedup anyway.
- Coding_Cat 9y agoraw number crunching doesn't parallel speedup(!)?
- phdelightful 9y agoThe parent might be saying that we already have some good techniques for speeding up raw number crunching in parallel, so it's not as desirable to add yet another.
- cle 9y agoDidn't say that, I said that we rarely need parallelization for raw number crunching. Developers use parallelization for coordinating expensive IO way more often, and Java 8 streams solve almost nothing for that. Still need to know and worry about other Java concurrency primitives like volatiles, monitors, thread pools, etc. and all their pitfalls (race conditions, deadlocks, etc.). You should still read JCIP, it is still highly relevant in Java-land. Java 8 streams solved almost nothing in terms of concurrency (in fact they probably created more problems than they solved...). You should still be scared of concurrency in general, and particularly in Java. And you should definitely consider a different language with more sane and modern concurrency primitives if you really need concurrency.
- peheje 9y agoAh ok. I was confused by the reponse to slaymaker1907 who recommended Streams directly, as it didn't seem to address the Stream API. I guess many of the challenges of concurrent computing still applies here. When else do we need parallel speedup?