He also admits he hasn't written more than a hundred lines of code with it before, and that was 4 years ago, more than half rusts lifetime ago.
My understanding is his priorities are C level control over memory, fast compiles, and ergonomics for the kinds of operations he commonly does.
Rust solves for memory/ergonomics, though the strictness it holds you to is in opposition to what (I understand) he considers ergonomic access & control of memory.
Therefore rust solves ~1 of his priorities, so it's not really a good fit.
To extrapolate that to "doesn't solve the hard problems" is another logic step that I probably don't agree with.
My understanding is his priorities are C level control over memory, fast compiles, and ergonomics for the kinds of operations he commonly does.
Rust solves for memory/ergonomics, though the strictness it holds you to is in opposition to what (I understand) he considers ergonomic access & control of memory.
Therefore rust solves ~1 of his priorities, so it's not really a good fit. To extrapolate that to "doesn't solve the hard problems" is another logic step that I probably don't agree with.