To me this seems like saying a webmail site shouldn't use SSL because the recipient might also use a webmailer and happily accept a self-signed certificate and bypass the browser warning. Sure, it's no replacement for E2E crypto, but to me that's a clear case of perfect being the enemy of good.
(I just tried it)
I just did for two of the author's comments, I don't think they should be dead at all.
1) The author states that their opinion changed somewhat
2) The author explicitly names a compromised deployment (Freenode). Haven't fact checked that, but that _seems_ like a good argument
3) The architecture of the network (random organizations sponsor servers) seems like a plausible excuse for headaches/complications as far as I'm concerned.