> you often don't have a way of enforcing your types on eventual consumers A type isn't something you enforce on consumers. It's something you enforce on your

> you often don't have a way of enforcing your types on eventual consumers A type isn't something you enforce on consumers. It's something you enforce on yourself to help shape your code. Regardless of how you put something onto the wire you're giving it a specific format that your consumers need to know about. This is the same whether it was serialised from Haskell or Clojure or Coq or assembly.