> If you embrace the type system and start modeling your domain types with the natural invariants in mind you start seeing the real benefit. Except that few ty

> If you embrace the type system and start modeling your domain types with the natural invariants in mind you start seeing the real benefit. Except that few type systems have the capability to do this in a reasonable way that doesn't lead to horribly contorted code full of type-induced damage. Just look at the difficulties that people have trying to express code at a higher level of abstraction like partial application, currying, generic composition, etc (as in fantasy land or ramda) in typescript. If you're acclimatised to working in a specific type system, you'll probably never notice the areas where it stops you legitimately abstracting. > entire categories of bugs will impossible to introduce. This is true. > Otherwise complicated architectures will become easy to express. This, I think, is false. In fact many complicated architectures (depending on your type system) will become impossible to express, and to some extent this is a feature rather than a bug.