4 ms·
Can you explain how that's not an aspect of developer experience? It seems to be like trading off between type system correctness (you can go all the way to nee
by ori_b 3y ago
Can you explain how that's not an aspect of developer experience? It seems to be like trading off between type system correctness (you can go all the way to needing full formal proofs of correctness, resource use, etc) and ease of getting stuff done is the core of developer experience.
- worik 3y agoWith Rust it is the learning curve that is hard. I find every other aspect of "developer experience" excellent
- jb1991 3y agoDoes your idea of a good developer experience include programs that are reliable, won't crash in production, won't be compromised, and save you lots of time later on so you can just focus on writing code the first time? In the absence of these guarantees, your developer experience can include some very frustrating and/or stressful debugging.
- ori_b 3y agoYes. Does yours not? Tools like Agda, Spark, Idris, and Coq move the tradeoff around towards "probably correct", and I welcome seeing some of their features become gradually available. Getting things right the first time is useful. But these features can also make it hard to get anything done quickly. Good developer experience means finding a balance between the quick and dirty, and the provably correct.