Typing Is Hard
I think we need new, better concepts to judge type systems by. Eg TypeScript has convincingly shown to a large crowd that soundness isn&#x27;t an important property for many key goals of static typing, such as programmer productivity, refactoring support, preventing stupid mistakes and navigating large codebases. Soundness was Flow&#x27;s big claim to fame and it just made day to day programming harder with mostly academic&#x2F;cosmetic benefits. I&#x27;m sure that there&#x27;s more reasons why TS won the popularity contest, but TS&#x27;s pragmatic forgiveness surely played a part.<p>And I don&#x27;t even see how &quot;decideable&quot; is a desireable property at all. So what if the type checker can infloop? It won&#x27;t in practice.<p>At the same time, most people will agree that eg Go&#x27;s type system is very different from Idris&#x27;s. They have very different pros and cons, both in terms of how hard they are to typecheck and how great they are to use. In fact I can&#x27;t think two somewhat popular type systems that could be more different from one another, but if you only read this page you might think they&#x27;re comparable.<p>We need words for &quot;totally anal&quot; and &quot;basically Ruby but some typos are caught&quot; and everything in-between.