3 ms·
There seems to be a nigh-irresistible urge for people, when explaining type systems, to pick examples that are absolutely useless. None of the types in the the
by roenxi 6y ago
There seems to be a nigh-irresistible urge for people, when explaining type systems, to pick examples that are absolutely useless.
None of the types in the theme here make much sense. They are arbitrary. The contribution to writing a robust program is questionable and they don't do much to explain concepts.
May as well stick with classic "Goats are mammals; that should be enough to get you going with OOP" examples, at least they are less distracting.
I'm not a fan of this article.
- ivanbakel 6y agoThat's a problem with the domain itself. Type system examples can be two of: short, concrete, well-motivated. Short concrete examples don't have time for motivation; concrete well-motivated examples require lots of text (or else are unreadable); and short well-motivated examples are forced to be highly abstract. There's no substitute for actually encountering a real-world problem which makes you want/need type-level programming. The article makes the sensible choice of not trying to invent one for you. I don't think it should be bemoaned for that.