The author gave his reason at the bottom of the article. I think I'm inclined to agree with him. The underlying problem isn't a symptom of something unique and

The author gave his reason at the bottom of the article. I think I'm inclined to agree with him. The underlying problem isn't a symptom of something unique and crazy that one unique AV vendor is doing. It's a symptom of something standard (but crazy) that enterprise AV solutions do. If monkey patching every process on the system at run-time is something you view as evil, then he's already named and shamed the entire antivirus software industry, and now you know to steer clear of antivirus. Which you were probably already doing, anyway, to the extent that IT lets you. If you see it as an inevitable part of running AV, and view AV as essential, then there's not really anything to shame. It was an honest bug relating to an obscure corner case. I hope they've already filed a bug report, so just keep your AV up to date and it should get fixed.