That's fine, but it doesn't help me with the errors that I make.
I don't make representation errors. I make kind errors. The difference is that the number of apples and the number of bananas are both non-negative integers, but a check for non-negative integers doesn't keep me from adding apples to my bananas inventory. Remember that I do want to add both apples and bananas to my fruit inventory.
Yes, I care about representation, but things shouldn't go south if I happen to have half an apple.
void DoSomething(Fuit fruit, uint quantity) { .. }
Inside that method you will be guaranteed to receive only apples or bananas and a non-negative integer for quantity.
But anyway, in many cases, structural typing can make more sense than name-based typing.
Due to these tradeoffs, in some cases, people can be more productive in a language without the help of a typechecker than they can in certain languages' static type systems.
C# is a little better than the big 3 (C, C++ and Java), but you still trade off between helpfulness and verbosity. F# is a lot better IMO, but it's still fairly obscure, so of course not many people are going to be using it.