I could not help myself with that one.
But attempting to be serious now, I work with Microsoft field engineers often and I like to ask them tons of questions about their opinions on the industry and where the technologies are heading. Just a couple weeks ago I was speaking with someone who was conducting training in Windows 10. In the class he brought up Hyper-V; on a brief technical note, he mentioned that the Hyper-V on Windows 10 is not as good and does not support nested virtualization, which is something we need for network hypervisor like Cisco's VIRL.
However, what surprised me is that he said that, feature-wise, Hyper-V in Windows Server 2016 is on par with only vSphere 4.1. This was coming from someone who is a trained evangelist. Also, he stated unashamed that Microsoft does not support a VDI solution of its own but instead endorses Citrix.
Of course, he still aggressively pitches Hyper-V despite its inability to match up to the vSphere features. Part of this argument is that Hyper-V ships out of the box as part of the Windows Server package and that it can integrate seamlessly with Azure. And of course, once we start trying to compare vCloud to Azure, there is no question about which has more hope for the future. The buzz on Twitter is that vCloud was sold and is on its way out. However, VMware will be getting an integrated solution with AWS pretty soon (this is in beta), and this should stand it up very well to anything that deploys out of Azure.
It is a compelling case for Hyper-V, pricewise, that if you are already using Windows Server and want to virtualize it that you would use the native Hyper-V. However, if you want a large and complex private cloud environment, then I would be curious as to how anyone would try to do that with Hyper-V.