I do not want to go into a mud-slinging contest or in any play on words. I value you as a person, and I value your contributions to this site and to the SQL Server community in general. But I do want to make sure that people are aware of the facts about quirky update. And these facts are:
1. The "quirky update" method is not documented (and in one KB article, Microsoft even explcitly warns that a very similar technique can produce unexpected results).
2. When you originally posted your first quirky update article, there was a short list of conditions that, according to you, guaranteed correct results. In the discussion that followed, many people showed code that stayed within those conditions, yet produced incorrect results. This eventually resulted in you pulling the article.
3. You later posted a new version of the article, with a much longer list of conditions - based on the feedback to your first version. And yet, there again were comments with code that observed all the conditions in the new list but still produced incorrect results. In the discussion that followed, people introduced a technique that tries to ensure that you will not get incorrect results by throwing a run-time error if you would. (As I said before, a technique that I considered reliable at that time, though I am not 100.000% sure if that still is the case when batch mode execution is used).
When you posted your first article, you were confident that your list of conditions was complete - but you apparently had overlooked some situations.
When you posted your second article, you were once more confident that your revised list was complete, and that the technique was now safe. And again it turned out that you had overlooked some situations.
Perhaps you have once more updated the list of conditions. Perhaps you haven't. To me, that is irrelevant. What matters is that history has proven that you are not infallible, and that your claims of quirky update being safe and reliable have been disproven twice. Why should I believe that this cannot happen a third time?
The quirky update method is not terrible. It has its merits, and there may be places where it is the best solution. But anyone who choses to implement this method has to be aware of the risks, and be willing to accept this.
Any claim that quirky update is safe and reliable is simply wrong.