Then 90% of Modern apps are then badly designed and MS has completely failed to remind them and their own devs. They aren't navigable with the keyboard alone. For all your bitching about how the Desktop isn't friendly to the keyboard. Metro is even more reliant on a blah blah blah pointing device (precise mouse or coarse touch). You can play the 'blame the app' game, but that only works in open ecosystems. Living in the walled garden that no one is maintaining. Loverly.
Win8's voice support isn't a shadow of what is on Xbone or with Cortana. Which is arguably willful crippling of Win8 as a HTPC.
Agreed - voice-control IS horribly under-utilized, and not just in ModernUI, either.
However, I'm not excusing Win32/Win64 for bad application design, either - as much as you would like to think so.
What I am saying is that bad application design - regardless of API - is a major problem. However, it is more easily "forgiven" in Win32 because it remains the majority API, and the design flaws in the applications reflect the biases of the majority of the API's userbase. We accept flaws in Win32/Win64 that we treat with scorn in Modern - why?
I have not said that ModernUI applications are flawless - that is something I have never said. My issue with the pointing-device-centric (from an API standpoint) is that they are more accepting of flaws in Win32/Win64 than they are in ModernUI, simply because the older API "kisses up" to their biases. That shouldn't be tolerated, either.
I have not hesitated to whack ModernUI applications for faults - if you have followed my posts, you would see that.
However, how many of you will criticize a Win32 application for those same faults - for which there is far less excuse?