"Alert is bad" - really?
<p>There's this idea running around that "alert() is <strong>bad</strong>".  </p>

<p>Acknowledgements:</p>

<ul>
<li>Sure, we rarely want to use it in an actual UI design since there are better ways to communicate with users.</li>
<li>For debugging, <code>console.log()</code> has much more value than <code>alert()</code>.</li>
<li>Certain situations (like use of <code>setTimeout</code>) run into problems when <code>alert()</code> gets in the way.</li>
<li>Actual debuggers handle pausing and resuming of execution much better than <code>alert()</code>, if that's what a developer needs.</li>
</ul>

<p>Questions:</p>

<ol>
<li>Is there a solid, logical reason to <em>never</em> use <code>alert()</code>?</li>
<li>Does the increased value of <code>console.log()</code> truly reduce the value of <code>alert()</code> so drastically that it goes from "useful in limited scenarios" to "bad"?</li>
<li>What do you say to someone who wants to use <code>alert()</code> in a brief test where logging is not setup and any side effects are irrelevant (think tutorials or quick prototypes)?</li>
</ol>
