Objective. Right....
UWAs cannot be distributed and installed easily without going through Microsoft as the gatekeeper.
Simply not true. Valve could install their certificate during steam's installation and distribute UWA's just like the windows store, without any MS gatekeeping. (My bet would be that valve wouldn't want to sign and take responsilbility for the games/software they sell on their store)
The unfair part is that the MS certificates and store come pre-installed with windows 10.
From the tests i did, I didn't actually see any restrictions on interfering with the executable at runtime. Cheat engine works, WinDbg works, and as far as i can tell dll injection works as well.
A new API will require a new set of tools. Expecting the old set of tools to work, and when it fails claiming it's impossible seems like rushing to conclusions to me.
Another very common use of this type of interoperability: the overlays
Oh wait, he forgot to mention another very common use of this type of interoperability: malware and keyloggers. I would even argue that more people are negatively impacted by those than by the lack of an fps counter (assuming, for the sake of argument, those things are really impossible).
I see UWA as the xbox ecosystem on PC, in addition to the standard win32 API.
I can't imagine companies dumping 20 years worth of code to switch to a new, financialy unproven store/platform. And I can't see MS forcing devs to do that either, it's just not financially viable.
Maybe over a period of ~10 years, MS could decide to deprecate win32. But I expect that by then, either UWA will be changed to be more developer friendly, or it will be dumped in favor of another format (like linux's ELF, or something similar to android's VM).
I guess the biggest fear In this scenario would be that the vast majority of people wouldn't care about UWA's restrictions, and it will get adopted "as is" as standard. Personally, I don't see this happening.
Edit: UWA has it's negatives. But ithink that people are grossly over reacting.