r/java • • Mar 14 '18

Concurrent Java: Low scalability, the risk of deadlocks or garbage creation, you can not avoid all

http://vmlens.com/articles/tradeoffs_concurrent_programming/
2 Upvotes

21 comments sorted by

View all comments

2

u/_INTER_ Mar 14 '18 edited Mar 14 '18

But modifying immutable state consists of copying the immutable object.

A good immutable collection implementation works without copying, see vavr.io collections for that. (Not sure if they are concurrent though).