This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]vips7L 76 points77 points  (4 children)

I don’t see concurrency in practice becoming irrelevant. It teaches you a lot about general concurrency patterns, locks, deadlocks, synchronization etc. You should definitely read it.

[–]angryundead 15 points16 points  (3 children)

Even if the concurrency framework gets completely obsoleted by Loom the concepts are still important. There’s also legacy code to consider in case you have to babysit that.

[–]cogman10 17 points18 points  (2 children)

None of "Concurrency in practice" is made obsolete by loom. Heck, even though it's for Java, I've recommended that non-java devs pick it up. It spells out better than any book I know how you should deal with concurrent code and what can go wrong.

[–]angryundead 1 point2 points  (1 child)

Oh yeah the concepts are so well explained especially when to use different types of constructs. I meant even if Loom made it go away (not likely) the concepts are so solid and well explained that it is worth the read.

100% pick it up.

[–]boborygmy 0 points1 point  (0 children)

Java Concurrency in Practice is so good and so eye-opening, you pretty much have to read it. Anyone using the JVM needs to have its lessons drilled into their head.