3 ms·
> coding when EVERYTHING is immutable by default is a royal pain in the arse Not sure I'd agree with that. Scala is a pain to write at times, but it's not beca
by eropple 9y ago
> coding when EVERYTHING is immutable by default is a royal pain in the arse
Not sure I'd agree with that. Scala is a pain to write at times, but it's not because of the immutable data structures--indeed, the APIs are structured such that it's pretty painless. And while under the hood Kotlin's "immutable lists" aren't actually immutable (they're just ArrayLists, the interface is more akin to C#'s IReadOnlyList<T>), the API they present on top of it makes this pretty straightforward.
In both cases, you can do mutable things, but it's extra work.
I tend to think it's more of a Clojure-specific thing, and I think your #2 is more to the point: people don't use Clojure because it looks funny and is foreign to read for people who don't already know Lisps, that's all.
(I've used Clojure, but I don't claim to "know" Clojure. YMMV.)