Yeah no thanks. I'm not going to read something so fair-minded as to call those with whom it disagrees "anti-vaxxers". Winer has a point that resonates with many people. You're not going to convince them by calling them idiots.
In this very thread I've gotten my fill of juvenile down-talking: "you must not understand how HTTPS works!" "Security is good, m'kay?"
The points that Winer has made are more subtle than this. Any convincing rebuttal would be more subtle. That title is if anything less subtle. If there were a point at that link that was actually responsive to Winer, I presume you would have quoted it.
I didn't see anyone here say "you must not understand how HTTPS works!" or "Security is good, m'kay?". I'll take it in good faith that the comments you quoted are only missing because they got deleted since, or maybe there is some misunderstanding.
If you scroll down the article by Scott Helme, you can see that he does respond to Winer specifically. Here is the link with a fragment that goes to that section of the article:
Since you insisted, I clicked through, and read until I got to this gem:
Google has never said they're going to deprecate HTTP, the only things that have been said are around changing visual indicators for HTTP and HTTPS in the browser...
Perhaps the word "deprecate" has some idiosyncratic personal meaning for this yokel. I've seen the over-the-top warnings Google came up with for valid self-signed certificates, and their warnings for no certificate at all won't be much relaxed in comparison. The most popular browser loudly insisting that users never go to non-TLS sites would certainly be a deprecation.
