> It may be safer, but not as "ergonomic" subjectively, which ultimately affects productivity. Tit for tat. When you gain particular categories of guaranteed c

> It may be safer, but not as "ergonomic" subjectively, which ultimately affects productivity. Tit for tat. When you gain particular categories of guaranteed correctness there are things you needn't worry about, and that saves you lots of trouble down the road. How much ergonomical pains such a gain is worth is obviously debatable, but I think it's absolutely reasonable to say that trading guaranteed correctness for comfort more often than not is going to be the right thing to do in systems-level programming. And the lower-level you go, more so.