title: Why does console.log not appear to enter the event queue if it is a Web API?
body: <p>Most examples explaining the concurrency model of JavaScript in the browser list three parts: The call stack, the web api's, and the event queue. The normal process which is often described is that Web APIs are not handled by core ECMAScript and are handled by a web API; at this point they move into the event queue to wait until the call stack is empty to be executed. <code>setTimeout</code> is often used as an example to this process.</p>
  
  <p>My questions are:</p>
  
  <p>1.) since console.log is a web API, why does it not enter the event queue behind setTimeout? (does it even enter the event queue at all)? </p>
  
  <p>2.) If it doesn't enter the event queue, what determines what APIs get pulled out of the call stack to go through the event loop process? Is it only those APIs which wait for something and have callbacks?</p>
  
  <pre><code>setTimeout(function(){
    doSomething();
  },0);
  
  console.log('Hello World!');
  </code></pre>