[Haskell-cafe] What puts False before True?

[PR Stanley]

> >I think it's mathematical convention more than the C convention Haskell
> >is agreeing with.
>
>I think so, too. In Boolean algebra (which predates computers, much less
>C), FALSE has traditionally been associated with 0, and TRUE with 1. And
>since 1 > 0, TRUE > FALSE.
The question, however, still remains: why False = 0 and True 1? I 
appreciate that it's so in boolean algebra but why? Why not True = 0 
and False = 1?
A Boolean value denotees veracity whereas an ordered value concerns 
magnitude (priority), indeed, order!!
Thanks,
Paul