The Anti-Human Consequences of Static Typing

Re:The Anti-Human Consequences of Static Typing by dragonwriter on Monday August 12, 2013 @04:57PM (#6201847)

> To take a simple example from Python, there are plenty of cases where you want a function to return either a string, say, or None, depending on whether it is able to find a string meeting some set of criteria, and you can't use the empty string as your "not found" value because empty strings are semantically significant for your application.

Static typing is not a problem here. Static type with an inadequate type system is a problem here,

[ Parent | on HN ]

Re:The Anti-Human Consequences of Static Typing by kbenson on Monday August 12, 2013 @05:32PM (#6202156)

And that's the whole point of his post. Don't let strict adherence from static typing overshadow interesting new techniques from being developed when we don't use static typing. We can then go back and update our type models to allow that new usage. The first comment on the article (bottom of the list of comments) clarifies his purpose.

[ Parent | on HN ]