> It breaks badly designed text protocols - some can argue that it's a good idea - "crash early, crash loud" etc This is decisively not a case of "fail loudly"

> It breaks badly designed text protocols - some can argue that it's a good idea - "crash early, crash loud" etc This is decisively not a case of "fail loudly", which I agree is generally a good idea. The very first example in the article is one of silent incorrect/ambiguous output, not loud failure.