←back to thread

Flattening Rust’s learning curve

(corrode.dev)
452 points birdculture | 1 comments | 13 May 25 22:25 UTC | HN request time: 0.253s | source
Show context
jmull ◴[14 May 25 13:59 UTC] No.43984646[source]▶
I'm not sure there are many cases where I would choose rust. I'm open to it. I just think in any given situation there would most likely be a better option.

Perhaps it will become prevalent enough that it will make sense in the future.

replies(4): >>43984813 #>>43985214 #>>43985593 #>>43986622 #
1. coldpie ◴[14 May 25 14:49 UTC] No.43985214[source]▶
It's the best fit I'm aware of for any task where correctness is worth the dev time hit. That includes systems programming tasks, where you're shuffling memory and files and system resources around and an error could kill your program or corrupt resources; or as a library for critical parts of your program, which could then provide an interface for other languages to use that allow for faster development & prototyping.