I have no problem with you preferring .NET to Java, and I apologize that my first-cited article was not the best one to share to describe the problem (I should

I have no problem with you preferring .NET to Java, and I apologize that my first-cited article was not the best one to share to describe the problem (I should have read it more carefully first), but if you had responded with something like: "Your deadlock scenario is related to synchronization contexts and can be avoided by ..." rather than: "You clearly don't know what you're talking about (but I won't bother telling you why)" Then we could have had a much more productive and pleasant conversation. I would have responded with: "Sorry, that article wasn't the right one to share. Here is a better one. The issue I am talking about isn't synchronization context-related at all. It's actually much more insidious."