←back to thread

Flattening Rust’s learning curve

(corrode.dev)
451 points birdculture | 1 comments | 13 May 25 22:25 UTC | HN request time: 0.257s | source
Show context
ajross ◴[14 May 25 02:41 UTC] No.43980170[source]▶
> Use String and clone() and unwrap generously; you can always refactor later

At that point you might as well be writing Java or Go or whatever though. GC runtimes tend actually to be significantly faster for this kind of code, since they can avoid all those copies by sharing the underlying resource. By the same logic, you can always refactor the performance-critical stuff via your FFI of choice.

replies(5): >>43980203 #>>43980432 #>>43980632 #>>43981812 #>>43981902 #
1. landr0id ◴[14 May 25 02:45 UTC] No.43980203[source]▶
So long as you're aware that you're not optimizing, it's fine. Trying to build something useful as a new Rust dev while worrying about lifetimes is going to be quite challenging, unless your intention is to specifically learn about lifetimes and the borrow checker.

Yes the borrow checker is central to Rust, but there are other features to the language that people _also_ need to learn and explore to be productive. Some of these features may attract them to Rust (like pattern matching / traits / etc.)