Thread:User talk:CodeCat/"I don't understand this crusade against script errors..."/reply (4)

> I really don't see any value in hiding errors. Errors are errors, and you can't make them not errors. You can make them look nicer, but you can't hide the fact that something went wrong.

I completely agree.

"Script error", however, is not the only alternative. It shouldn't even be on the table. With the path we're going down, we're on our way to replacing whole pages with "Script error" just because of minor errors. (Consider your recent proposal to wrap whole definitions in . What happens when a typo results in ]} instead of &#x7D;}, and suddenly a single is trying to process three definitions and all their example sentences and quotations? Should the whole thing blow up in "Script error"? Or should  try, just a little bit, to not break everything?)

You say "trying to have our cake and eat it", I say "not actively shooting ourselves in the foot".