Yep, I’ve seen this in Swift with a dozen overloads for functions and class initializers to support umpteen similar, but different, types as input. Sloppy schema design reveals itself in combinatorial explosions of type conversions

Yes. I don't understand why HN reacts with such froth to the suggestion that this problem runs deeper than type systems.