[packetlost]

> When you are dealing with real world concurrency i.e. error/thread management Rust’s memory management model becomes unusably complex very quickly

I've seen this several times, but having built several highly concurrent applications in Rust, I just don't agree. Building a concurrent Rust application the wrong way is certainly complex, but if you know how Rust's strong opinions on how to structure an application work, it's downright pleasant.

Except async. Rust's async story still sucks and should be avoided as much as possible.

[threeseed]

Compare this to Scala and it just doesn't matter about right/wrong way.

It all just works without issue. Maybe you use a few more CPU cycles garbage collecting but these days it's unnoticeable.

[packetlost]

I'm not speaking bad of Scala or the JVM: I actually agree. When the GC and overhead don't matter, a JVM language is an absolutely fantastic choice. I was more commenting that Rust can be simple if you architect it right, that's all.

I've mostly come to the conclusion that a mediocre engineer can write performant enough Java/Scala/Clojure/Kotlin/etc. Usually even more performant than what an inexperienced/mediocre C/C++/Rust engineer could write and have an easier time doing it. However trying to ilk out the last bit of performance in a JVM language can be very challenging.