3 ms·
This is pretty much the worst case scenario in the fight between maintaining nice, human readable error messages for unsophisticated users and ugly, information
by InclinedPlane 17y ago
This is pretty much the worst case scenario in the fight between maintaining nice, human readable error messages for unsophisticated users and ugly, information dense technical error messages for aiding debugging for technical users (and developers). The result here is a message that helps neither users nor developers understand what went wrong or how to fix it. A message such as "fault in module Foo @ address 0x921851" or somesuch would be no more incomprehensible to the average user than this and a message such as "something went wrong, oh noes!" would be no more useless to developers. As it stands it's only through the magic of the internet and the fact that, thankfully, this message is at least a little unique that people are able to find out what this message really means and how to fix it.