But I'm not going to try to guess what you wanted to say and then discuss that, because I'll probably guess wrong.
Instead of complaining when people point out that what you said was false, you should thank them for taking the time to correct you and take the opportunity to learn from it. Then, be more careful about what you say next time, so that you say things that are true instead of false.
So you should carefully read and consider the conversation before you write, least you come across as arrogant and foolish.
Whether this works or not—or, more defensibly, how great the risk is—depends a great deal on the details.
I'm not really interested in how I appear to you, so I recommend you don't waste your time telling me about it.
But I don't think this is a technical conversation anymore, you have some other problems to address and it is best you do that.
As for whether this is a technical conversation or not, I think there's an interesting split: all of my comments in this conversation have been technical, and informative to boot, while the technical content of your comments has been limited to trivial statements that are easily shown to be incorrect.
Instead, your last two comments have contained personal attacks, which I have so far refrained from. (You may have noticed in the past that, when you repeatedly launch personal attacks on people, they usually respond by personally attacking you too, but I have not done that.) Your latest comment is over 50% personal attack by byte count.
Why is that? Have you considered thinking long enough about one of your comments to post something technically correct, original, or both?