846 karma · joined March 21, 2014
Good type systems increase velocity by leaving less room for error, so that you don't have to waste half your time debugging and fixing issues that could have been easily prevented. They also provide helpful structure and an IDE experience (the right values, functions, actions, etc are actually suggested for you wherever you are) that really does speed up development a lot.
There's of course always a trade-off: bad type systems can get in your way with boilerplate that you have to wrangle. But I don't think that's the typical experience.
What are you talking about? I've never heard this take before. I found it fantastic all the way through. Maybe introducing the lord vessel was a poor design choice, but it's a minor fault.
The most famous example can be found at the bottom of this page: https://www.alphadictionary.com/fun/tongue-twisters/swedish_...
å: stream
ö: island
i: in
ä: not correct, but used to represent dialectical pronunciation of "är", i.e. "is"