Every additional nine of not getting hacked takes effort. Getting to 100% takes infinite effort i.e. is impossible. Trying to achieve the impossible will make you spin on the spot chasing ever more obscure solutions.

As soon as you understand a potential solution enough to implement it you also understand that it cannot achieve the impossible. If you keep insisting on achieving the impossible you have to abandon this potential solution and pin your hope on something you don't understand yet. And so the cycle repeats.

It is good to hold people accountable but only demand the impossible from those you want to go crazy.

While for many applications Clojure's performance is good enough it's not anywhere near what you can achieve with Rust. I once did a small game in Clojure trying to be very clever to eke out every last bit of performance and still didn't hit an acceptable frame rate. Made a very naive reimplementation in Rust that involved copying the entire state every frame and it run buttery smooth.

If there is a task for wish persistent data structures are the most performant solution it should be easy enough to implement and use them in rust too. Probably someone already did that.

Clojure is my default programming language but if I want performance (or static types) I reach for Rust.

Translating is a completely different skill that you have to train on top of being fluent in more than one language. The way I translate is by sort of forgetting something in one language and then remembering it in another. It's a slow and awkward process but I suspect if I did this for like a thousand hours hearing something and then repeating it in another language would be as easy as switching the language in which I'm thinking. I think the real difficulty of simultaneous translation comes from having to speak while you're listening. Consider recording your response to an audio message while listening to it, that would also be very difficult but there is only one language involved.