There's no need to make up some wild conspiracy theories with Windows here, spend a single Google search before going into this direction next time.
I have seen significant changes in the policies established only just weeks ago that should enable Qualcomm to better participate in developer communities. There's a clear message from the CEO and several VPs that these changes are necessary.
Forgive me the snark, but I'll believe it when I see it. The last years didn't inspire me with confidence.
The problem is, at the core, that this sort of behavior used to be the norm in the industry. Working with embedded systems is pure and utter hell. The open documentation and standardized interfaces one got with Intel/AMD is the complete exception.
Indeed, it will be hard to change the minds of all the folks at Qualcomm who have operated here for years under the status quo. I see new leverage for those who have lobbied for change in the past.
I'm cautiously optimistic.
Qualcomm let Apple steal it.
Qualcomm's competition isn't Apple. It's Intel and AMD. Intel and AMD offer chips that run Windows much better than whatever Qualcomm can make. Apple managed to do that because they control the whole stack - they made macOS run well on ARM, something Microsoft has little incentive to do because chicken and egg.
For Windows, binary compatibility with 3rd party apps is extremely important, at least for the apps that aren't browsers running JavaScript, so, what Qualcomm could aim to do is to optimize the heck of their ARM offerings for x86 emulation/JITing, and efficient JavaScript execution, more or less what Apple did.
I found this remark by HN user dwaite very informative: https://news.ycombinator.com/item?id=37327938
TL;DR emulated x86-32 performance on ARM is poor, and is going to stay poor because of the memory model. Whether this strategy is going to be successful largely depends on how important/prevalent legacy 32bit apps are.