2 ms·
Working software doesn’t always have to be correct or safe. This is highly use case dependent. Rust’s guarantees aren’t free, it comes with a handful of tradeof
by catlifeonmars 2y ago
Working software doesn’t always have to be correct or safe. This is highly use case dependent. Rust’s guarantees aren’t free, it comes with a handful of tradeoffs, such as learning curve, implementation speed, (this one is personally annoying) compilation speed, and portability. I’m a huge proponent of using the right language for the job. Sometimes rust is the obvious choice, sometimes it’s Python, Go, Lua, Java, Prolog, C, brainfuck etc.
- tylersmith 2y ago[flagged]
- suby 2y agoYou are really being a jerk in this entire thread. Here is an 18,000+ word article on one domain where Rust is not a great fit. https://loglog.games/blog/leaving-rust-gamedev/ https://loglog.games/blog/leaving-rust-gamedev/
- placebo 2y agoWorking software and correct software are two different things and understanding that like in most things there is a tradeoff might be beneficial.
- pdimitar 2y ago> Working software doesn’t always have to be correct or safe. I feel like I am missing some very obvious point of yours because that statement in isolation I cannot agree with (I've read the rest of your comment and still can't find the extra context). Can you clarify?
- catlifeonmars 2y agoLet me define the terms I used to see if that clears it up at all. Working software: Does the software satisfy the use case? Correct or safe: does the software enter into any invalid states? Are edge cases handled? Does that help?