I think, especially in programming language communities, that there tends to be a preference towards making a static language for their compile time guarantees, and this is a pretty concrete counterargument as to why people find dynamic languages “easier to program in”
I have mixed feelings about the blog post. I don’t think it is wrong per se, but I think this text conflates language features that are orthogonal too much. The initial description of the problem is good, explaining what is meant by inconsistency and feature biformity. But there’s a lot of things after that I just don’t agree with. Maybe there’s some different core assumptions to start with we disagree on.
But in the end, different tools require different features. Programming languages are tools. There’s no one-size-fits-all solution to every use case.
I do not understand “counterargument” here either. Counterargument for what? I don’t think anyone suggests that choice of typesystem isn’t a tradeoff.
Maybe not here, but I tend to get the feeling that the argument for static typing goes “it may look harder than dynamic types, but it’s really not that bad”, where as this article shows some more concrete disadvantages of static type systems