I'm not feeling the async pressure
I wish he would have commented on .NET&#x27;s async implementation. Microsoft really got it right here and it&#x27;s arguably the best implementation I&#x27;ve seen.<p>All .NET async APIs take an optional cancellation token parameter which solves his flow-control problem by allowing the async request to be canceled at any time. If the token is canceled, the async task will (or should) throw an OperationCanceledException which can then be cleanly handled in a standard try&#x2F;catch block up the stack.<p>The best part about this is that it pervades the entire .NET runtime, the APIs, code examples, and has excellent documentation on correct usage patterns. Sure, a 3rd party library could choose not to support cancellation tokens, but they would be going against the entire .NET ecosystem by doing so. Every other async implementation I&#x27;ve seen has really seemed like a haphazard bolt-on.<p>I honestly don&#x27;t know how I would write robust async code without cancellation tokens, so I guess he has a point when it comes to javascript and python ecosystems.