3 ms·
*Caveat For me, typed code is more readable than untyped code. As someone who writes & is very used to typed code. Thinking back to a previous iteration of my
by lucideer 4y ago
*Caveat
For me, typed code is more readable than untyped code. As someone who writes & is very used to typed code.
Thinking back to a previous iteration of myself, learning C/C++, Javascript & (old, hint-less) PHP in my early 20s, typed code looked alien. Sure, if I'd applied myself a little to the reading, I guess I could've figured it out pretty easily, but I wasn't inclined to because it appeared impenetrable to me. In a similar way to regex or terse perl (though not as bad obviously).
TL;DR: It needs the advocacy because the readability gains aren't obvious/implicit.
- User23 4y agoI find Haskell to be strongly typed and hard to read.
- lucideer 4y agoSame argument re: familiarity really. The question is: if there were a weakly typed haskell (same/similar syntax & conventions, no strong typings), which one would a person familiar with haskell find easier to read? Effective readability has two components: familiarity, & actual readability. We'll automatically find everything unfamiliar to be less readable, but once we're familiar with all options, which is most readable then?
- hoosieree 4y agoI love how this thread is making a type error about the word "type". I upgraded my keyboard from Cherry Red to Blue, so my Haskell is now strongly typed.
- simplify 4y agoAgree that familiarity is important. The "actual readability" you mention I call "communication" in my post breaking down readability[0]. Self-awareness on familiarity is important for any developer to have before declaring code as readable or unreadable :) https://gilbert.ghost.io/dissecting-code-readability/ https://gilbert.ghost.io/dissecting-code-readability/