[dianeb]

Define what you mean by "everyone" -- there are times where the cost of immutability can be overwhelming, such as in high traffic systems with overly complex data structures which you are required to use because someone who should have known better insisted upon writing.

(sorry, bitter personal experience) And yes, that is explicitly "modern" Java code written by a lead engineer and "java champion" in 2023.

[deepsun]

Yes, I feel you. As I said, we often need to sacrifice immutability to performance, and that's ok. If they insisted using immutable structures in high-performance applications, then functional programming won't help anyway.

[fhasdfyuasd]

Hopefully we won't have to make that trade off for too long

https://www.microsoft.com/en-us/research/uploads/prod/2020/1...

[deepsun]

Even reference counting needs memory management. Granted, allocations are very fast on the JVM heap, but cannot be faster than no allocations.

[codethief]

Came here to write this.

There's also a (research) language that uses the Perceus algorithm: https://koka-lang.github.io/