Ahh.... lovely, thank you.  So what I&#x27;m referring to as &quot;asynchronous javascript&quot; is technically a colloquialism used to describe the event-driven callback-y nature of the code.<p>I&#x27;m not sure I&#x27;m still against referring to javascript as asynchronous or at least as having asynchronous methods for the purposes shorthand and quick communication.<p>Consider the code (or paste it into a chrome console)<p><pre><code>     function _done(){ console.log(arguments) }
     var db = window.openDatabase(&quot;dbfoo&quot;, 1, &quot;test db&quot;, 5e6)
     db.transaction(function(tx){
        tx.executeSql(&#x27;CREATE TABLE t1(a, b PRIMARY KEY);&#x27;, _done, _done)
     })
     console.log(&quot;i happen before the line above me&quot;)
</code></pre>
Notice how the lines of code complete out of order. I think it&#x27;s really useful to think of that as asynchronous code. It appears I&#x27;m using async as a term interchangeably with non-blocking... which may not be correct. So it may be the case that my nomenclature is off, but I&#x27;m sure I got that from somewhere. Perhaps a lot of people were referring to node as async in the early days, I&#x27;m re-watching this: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ztspvPYybIY" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ztspvPYybIY</a> now, but it doesn&#x27;t look like Ryan Dahl uses the term async.<p>Anyways, looks like I&#x27;ll have to train myself to use the right word for it. Thanks for pointing that out without making me feel dumb or being all insulting and internet-y.  :) I really appreciate that.<p>EDIT: Hmmm... additionally, to be fair: it appears that some agree that it is OK to refer to parts of javascript as async <a href="http:&#x2F;&#x2F;stackoverflow.com&#x2F;a&#x2F;16524240&#x2F;398055" rel="nofollow">http:&#x2F;&#x2F;stackoverflow.com&#x2F;a&#x2F;16524240&#x2F;398055</a> so it might not be perfectly accurate, but it isn&#x27;t wildly inaccurate either.