Eric Blake wrote:
Knowing the pitfalls makes it easier to justify why an output that is
unambiguous was chosen as the new default over the previous ambiguous
output; any further changes to the default are now a matter of
fine-tuning about how much (or how little) decoration we can get away
with, while still avoiding a regression to the situation of ambiguous
output.
---
That's bull! You don't just randomly change
output in programs and break compatibility. If the user
wanted unambiguous, there are already options.
