title: Golang blocking and non blocking
body: <p>I am somewhat confused over how Go handles non blocking IO.
  API's mostly look synchronous to me, and when watching presentations on Go, its not uncommon to hear comments like "and the call blocks"</p>
  
  <p>Is Go using blocking IO when reading from files or network?
  Or is there some kind of magic that re-writes the code when used from inside a Go Routine?</p>
  
  <p>Coming from a C# background, this feels very non intuitive, in C# we have the <code>await</code> keyword when consuming async API's.
  Which clearly communicates that the API can yield the current thread and continue later inside a continuation.</p>
  
  <p>So TLDR;
  Will Go block the current thread when doing IO inside a Go routine, or will it be transformed into a C# like async await state machine using continuations?</p>