Should log() be used in place of try/throw/catch when 'bubbling up' is not needed?
<p>I have a function that wraps console.log like this.</p>

<pre><code>NS.log("error");
</code></pre>

<p>which I use for error logging.  It is a simple one liner to let the app developer know that something went wrong.  It does not stop program flow and shows up unobtrusively in the console.</p>

<p>However, I've heard in university courses, etc., that using a try/throw/catch is best practice as it uses an error control system already in place.</p>

<p>However, I don't need the error to "bubble" up after a throw statement.  I would catch it immediately like this:</p>

<pre><code>try {
    throw "error"
} catch (e) {
}
</code></pre>

<p>Are there any cons to simply logging the error as opposed to using a more formal structure.</p>

<p>My assumption is that try/throw/catch is for more complex structures.</p>

<p>But I wanted to make sure.</p>

<p><strong>Notes:</strong></p>

<ul>
<li>requirejs uses throw a total of 4 times | no use of console or log</li>
</ul>
