Same reason I always felt extremely comfortable with concurrent programming in F#. The immutable first principle makes it easier to reason about what the program is doing during concurrent execution.
Of course all projects will benefit from Loom. I am merely positing that Clojure in particular could leverage this both most quickly and to very deep positive effect, due to the nature of the language itself putting immutability first, which if I recall correctly they built up a pattern of concurrent execution around already.
Kotlin too will be be able to optimize their concurrency story.
I simply wanted to posit an observation I hadn't seen elsewhere on the web about Project Loom yet.
Of course all projects will benefit from Loom. I am merely positing that Clojure in particular could leverage this both most quickly and to very deep positive effect, due to the nature of the language itself putting immutability first, which if I recall correctly they built up a pattern of concurrent execution around already.
Kotlin too will be be able to optimize their concurrency story.
I simply wanted to posit an observation I hadn't seen elsewhere on the web about Project Loom yet.