> Then first class constructs like HttpClient are async, so devs are forced to either do the wrong thing or use an older, far less commonly used class to achiev

> Then first class constructs like HttpClient are async, so devs are forced to either do the wrong thing or use an older, far less commonly used class to achieve the same thing. That's not what "forced" means. That's a choice. > "Viral" features than can't be introduced incrementally in a code base should be a non-starter. This is the "forced" case. No choice.