"The performance of .NET and UI applications can be improved by using ConfigureAwait(false)."
Uuhhh. That's a way more complicated topic than you make it out to be. In a post that spends no time whatsoever talking about synchronization contexts giving such an advice is very illadvised.
Hey there, thanks for pointing out how my statement may be misread! Yes, I'm aware of the complexities involved so I cited Stephen Cleary's answer from SO.
What I really wanted to say is that: You can, but that doesn't mean therefore that you should do it.
Meanwhile, I've removed this statement. Does this convey the message clearer?
The performance of .NET and UI applications can be improved by using ConfigureAwait(false). Things aren't as straightforward, however. Do take a look at Stephen Cleary's answer before doing so.
"The performance of .NET and UI applications can be improved by using ConfigureAwait(false)."
Uuhhh. That's a way more complicated topic than you make it out to be. In a post that spends no time whatsoever talking about synchronization contexts giving such an advice is very illadvised.
Hey there, thanks for pointing out how my statement may be misread! Yes, I'm aware of the complexities involved so I cited Stephen Cleary's answer from SO.
What I really wanted to say is that: You can, but that doesn't mean therefore that you should do it.
Meanwhile, I've removed this statement. Does this convey the message clearer?
Edit: I'll include Cellivar's link as well.