Hi Philippe,<div><br></div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">In theory yes, in pratice no. You need to to async all the way down and<br>

then all the libraries (DNS, SQL, HTTP, �) need to be rewritten to be async.<br>
<br>
then<br>
 � �your<br>
 � � � code<br>
 � � � � � will<br>
 � � � � � � � read<br>
 � � � � � � � � � like<br>
 � � � � � � � � � � � this<br>
<br>
and exception handling is impossible. You can make it read like sync<br>
code again with continuations but you still have to solve the exception<br>
problem. At that point you have gained what exactly besides being<br>
trendy? Don&#39;t get me wrong, async has it&#39;s place but not in user code.<br>
Node has to be async because it has only a single process and a single<br>
green thread but we don&#39;t.<br></blockquote><div><br></div><div>Thanks for the hype busting and for clearest explanation I&#39;ve yet seen on Internet as to why Node.js is designed the way it as.�</div><div>The CSP analogy is interesting - I hadn&#39;t thought of it that way.</div>
<div><br></div><div>Nick�</div></div></div>