Why are web apps going crazy with await / async nowadays? : <p>I come from a back end / thick client background, so maybe I'm missing something... but I recently looked at the source for an open source JWT token server and the authors went crazy with await / async. Like on every method and every line.</p>

<p>I get what the pattern is for... to run long running tasks in a separate thread. In my thick client days, I would use it if a method might take a few seconds, so as not to block the GUI thread... but definitely not on a method that takes a few ms.</p>

<p>Is this excessive use of await / async something you need for web dev or for something like Angular? This was in a JWT token server, so not even seeing what it has to do with any of those. It's just a REST end point.</p>

<p>How is making every single line async going to improve performace? To me, it'll kill performance from spinning up all those threads, no?</p>
