Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Never patterns, exhaustive matching, and uninhabited types in Rust. Parent comment
From what I’ve seen, Rust prioritizes improvements in this order:
Refactoring code can be one of the hardest but most beneficial things a dev can do for a code base, so let’s make that simpler.
Reading code is done 10x more than writing code, so let’s make that intuitive.
Writing code can be tedious, how do we help make things ergonomic.
What this means is that the mentality of a weekend project, or any code you will write once and forget about is the worst way to try out Rust.
I’d recommend trying Rust twice. Once to create the first draft that might be shitty. Then again in a week or month to refactor that same code.
There are no comments on this comment yet.
From what I’ve seen, Rust prioritizes improvements in this order:
Refactoring code can be one of the hardest but most beneficial things a dev can do for a code base, so let’s make that simpler.
Reading code is done 10x more than writing code, so let’s make that intuitive.
Writing code can be tedious, how do we help make things ergonomic.
What this means is that the mentality of a weekend project, or any code you will write once and forget about is the worst way to try out Rust.
I’d recommend trying Rust twice. Once to create the first draft that might be shitty. Then again in a week or month to refactor that same code.