[repelsteeltje]

Beware, they are different concepts.

Threads offer concurrent execution, async (futures) offer concurrent waiting. Loosely speaking, threads make sense for CPU bound problems, while async makes sense for IO bound problems.

[groundzeros2015]

Why? You write the same code with async await but with a keyword at the beginning of every function.

[pkolaczk]

Only if you ever deal with one future at a time. But async allows things like awaiting one of N events in a very natural way. Those patterns are much less readable when done with threads.

[f_devd]

Because if you go down the callstack eventually you won't get the await keyword anymore; you'll get the actual 'waiters' and 'wakers' which define your scheduling

[groundzeros2015]

Yeah. The OS handles scheduling and preemption so it’s done for you rather than a call in the stack.