3 ms·
There is often an I love {Scala|Rust|Erland} post showing an simple type issue and claiming that using a bunch of new syntax would somehow fix it. <rant> 1.
by CharlesMerriam2 8y ago
There is often an I love {Scala|Rust|Erland} post showing an simple type issue and claiming that using a bunch of new syntax would somehow fix it.
<rant>
1. I want a minimum of typed syntax for safety. For example, remember Hungarian Notation? My linter barfs if I try "icCart = ipMyProduct" because of the semantic type issue.
2. I want a full set of primitives. For example, counts (c) are 0 or above, not infinite, can do arithmetic) while ids (i) are positive, not infinite, cannot do arithmetic, cannot assign constant). I want optionals; I want clearer error handling; I want fully declared I/O instead of manual error handling; I want better.
3. I want tallies of how often simple types are confused before changing languages to fix. My type confusions are complicated nested collections or variant records.
</rant>
Typing is a means for correct programming, not an end in itself.
- jpitz 8y ago>Typing is a means for correct programming, not an end in itself. That's not always the case. https://aphyr.com/posts/342-typing-the-technical-interview https://aphyr.com/posts/342-typing-the-technical-interview