←back to thread

Type checking is a symptom, not a solution

(programmingsimplicity.substack.com)
67 points mpweiher | 2 comments | | HN request time: 0s | source
1. moomin ◴[] No.45141951[source]
All of the examples in the article of “simplicity” involve the orchestration of complex platforms that are, for the most part, written using types. Try writing a browser that can pass Acid2 in Ruby and then try to convince anyone that what you’ve done is in any sense better than the Chromium codebase in all its complex glory.

Maybe the truth is that our job as developers is to manage the inherent complexity of the world we live in.

replies(1): >>45142241 #
2. guerrilla ◴[] No.45142241[source]
It's worse than that. Even ruby has types. They're just implicit and only checked at runtime.