I guess optional timestamps essentially boil down to the following: Client devs can no longer ignore the fact that there are problems with timestamps. They are free to choose to ignore these problems (i.e. by requiring them and ignoring unstamped messages), but it is no longer the default choice.

Which would prevent situations like @SoapDog's "I have no idea what happens". I'd consider that a vast improvement.