Why Concurrency Is Hard

Re:Why Concurrency Is Hard by Traubenfuchs on Tuesday November 10, 2020 @07:10AM (#25045072)

Modern, sane and productive languages usually come with strong abstractions for concurrent usage, e.g. atomic reference wrappers, thread safe wrappers (AtomicInteger) or special methods (Interlocked.increment) for numbers and concurrent collections.

With them and a basic understanding of single system concurrency, single system concurrency is and always will be trivial.

[ Parent | on HN ]

Re:Why Concurrency Is Hard by mrbald on Tuesday November 10, 2020 @07:16AM (#25045111)

They are low level abstractions and they don't save from the hardest to debug and fix problems - race conditions and inconsistent states, especially in distributed applications.

No mainstream languages give you a solid high level abstraction to build on. Some frameworks, kind of, do: ASIO in C++, AKKA Typed Actors and Reactive Streams and JDK CompletableFuture in JVM world, etc.

[ Parent | on HN ]