<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>magicalhippo</author><text>Indeed. Regular users have no idea what to do with &amp;quot;friendly&amp;quot; error messages telling them about some unrecoverable failure either, while they just leaves the techies with nothing to go on.&lt;p&gt;When raising exceptions in code, I make sure the error message contains as much relevant detail as I can stuff in there. Users will just mail a screenshot to support regardless (if they want help before the full error report gets home), so might as well give as much info as possible to make troubleshooting easier.</text><parent_chain><item><author>CharlesColeman</author><text>&amp;gt; In order for the document to help me, I clearly needed to find the four error parameters that used to be displayed with the blue screen on older versions of Windows. Windows 10 hides all the information by default, but I discovered that it’s possible to re-enable display of the extra error information by adding an entry to your registry.&lt;p&gt;I hate stuff like this.  What&amp;#x27;s the point of hiding the parameters, instead of tucking them away in the corner of the screen or something?  It just makes things needlessly difficult.&lt;p&gt;I know the answer is going to be &amp;quot;but it makes the UI look beautiful and most users don&amp;#x27;t know what the parameters mean anyway!&amp;quot;  Error UIs don&amp;#x27;t need to be beautiful, they need to be functional.  Definitely have a nice, clear user-friendly error message, &lt;i&gt;but keep the overall screen technically informative&lt;/i&gt;.  I can imagine that the only thing more infuriating than having a computer that won&amp;#x27;t boot, is having one that won&amp;#x27;t tell you the problem unless you change registry settings (which you &lt;i&gt;can&amp;#x27;t&lt;/i&gt;, because it &lt;i&gt;can&amp;#x27;t boot&lt;/i&gt;).  Leaving the extra information there does not harm, and it give people something to Google if they do run into a problem.</text></item></parent_chain></comment><story><title>Adventures of putting 16 GB of RAM in a motherboard that doesn’t support it</title><url>https://www.downtowndougbrown.com/2019/04/adventures-of-putting-16-gb-of-ram-in-a-motherboard-that-doesnt-support-it/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>spuz</author><text>Yes. What I can&amp;#x27;t understand is why this extra diagnostic information is not available with a keyboard shortcut, rather than with a change to the registry. If you get a blue screen on boot, you typically have no way to alter the registry. Holding shift or something would make much more sense.</text><parent_chain><item><author>CharlesColeman</author><text>&amp;gt; In order for the document to help me, I clearly needed to find the four error parameters that used to be displayed with the blue screen on older versions of Windows. Windows 10 hides all the information by default, but I discovered that it’s possible to re-enable display of the extra error information by adding an entry to your registry.&lt;p&gt;I hate stuff like this.  What&amp;#x27;s the point of hiding the parameters, instead of tucking them away in the corner of the screen or something?  It just makes things needlessly difficult.&lt;p&gt;I know the answer is going to be &amp;quot;but it makes the UI look beautiful and most users don&amp;#x27;t know what the parameters mean anyway!&amp;quot;  Error UIs don&amp;#x27;t need to be beautiful, they need to be functional.  Definitely have a nice, clear user-friendly error message, &lt;i&gt;but keep the overall screen technically informative&lt;/i&gt;.  I can imagine that the only thing more infuriating than having a computer that won&amp;#x27;t boot, is having one that won&amp;#x27;t tell you the problem unless you change registry settings (which you &lt;i&gt;can&amp;#x27;t&lt;/i&gt;, because it &lt;i&gt;can&amp;#x27;t boot&lt;/i&gt;).  Leaving the extra information there does not harm, and it give people something to Google if they do run into a problem.</text></item></parent_chain></comment><story><title>Adventures of putting 16 GB of RAM in a motherboard that doesn’t support it</title><url>https://www.downtowndougbrown.com/2019/04/adventures-of-putting-16-gb-of-ram-in-a-motherboard-that-doesnt-support-it/</url></story>