The author mentions letsencrypt, but their description of why letsencrypt is not a solution makes me think they have a less than complete understanding of modern SSL.
Also the configuration issue with regard to not supporting wildcard certs is not a problem IMO. If you're big enough to require multiple subdomains the fact that you're managing multiple certificates instead of one does not need to be a logistical issue. Automation is our friend.
I'd be a lot more willing to consider letsencrypt.org as a valid support for changing the fundamental requirements for communication on the rest of the web when it was a proven service whose practicality (and any pitfalls) for real users in a wide range of cases including those that weren't the most common was well-established, rather than an upcoming one.