3 ms·

1. I don't think it's going to explode the compatibility matrix... it seems to run unmodified x86 executables on ARM. They demo Photoshop running on a Qualcomm

1. I don't think it's going to explode the compatibility matrix... it seems to run unmodified x86 executables on ARM. They demo Photoshop running on a Qualcomm processor: https://www.youtube.com/watch?v=A_GlGglbu1U&feature=youtu.be https://www.youtube.com/watch?v=A_GlGglbu1U&feature=youtu.be 2. Existing "desktop app" authors can opt to package their app in a way that will make it possible to distribute through the Windows Store. https://msdn.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-root https://msdn.microsoft.com/en-us/windows/uwp/porting/desktop...

skrebbel 10y ago
You can also run 32-bit apps on a 64-bit OS (also because of an emulation layer), but still people offer 64-bit downloads of programs. Why? Speed and memory. With ARM it'll be similar.
- colemickens 10y ago
  I hadn't considered that. I assumed this was only x86 desktop apps on ARM via emulation. If they're going to let people build/distribute native ARM binaries for Windows 10... then I'm even more impressed. I guess I would've expected that to be mentioned though. If this is the case, that would certainly invalidate my comment about the compatibility matrix. I guess in that scenario, I'd agree and hope that those folks are working on a "fat binary" or "universal binary" or something to aid with the potential confusion.
  - mtgx 10y ago
    > If they're going to let people build/distribute native ARM binaries for Windows 10 Hasn't that been possible since Windows RT?
    - colemickens 10y ago
      Sort of. Windows RT only ran Microsoft-signed ARM binaries. Hence why I assumed it would've been an explicit announcement if they were allowing devs to distribute native ARM executables.
      - WorldMaker 10y ago
        Windows RT supported C/C++ "native" compiles for ARM, so long as you published it to the Store and used the WinRT runtime/lifecycle. It just didn't support Win32 binaries compiled to ARM outside of the exceptions for Microsoft's own applications. I don't think we have details if the new plans include allow developers to cross-compile Win32 apps to ARM, in addition to the x86 emulation.

skrebbel 10y ago

You can also run 32-bit apps on a 64-bit OS (also because of an emulation layer), but still people offer 64-bit downloads of programs. Why? Speed and memory. With ARM it'll be similar.

colemickens 10y ago
I hadn't considered that. I assumed this was only x86 desktop apps on ARM via emulation. If they're going to let people build/distribute native ARM binaries for Windows 10... then I'm even more impressed. I guess I would've expected that to be mentioned though. If this is the case, that would certainly invalidate my comment about the compatibility matrix. I guess in that scenario, I'd agree and hope that those folks are working on a "fat binary" or "universal binary" or something to aid with the potential confusion.
- mtgx 10y ago
  > If they're going to let people build/distribute native ARM binaries for Windows 10 Hasn't that been possible since Windows RT?
  - colemickens 10y ago
    Sort of. Windows RT only ran Microsoft-signed ARM binaries. Hence why I assumed it would've been an explicit announcement if they were allowing devs to distribute native ARM executables.
    - WorldMaker 10y ago
      Windows RT supported C/C++ "native" compiles for ARM, so long as you published it to the Store and used the WinRT runtime/lifecycle. It just didn't support Win32 binaries compiled to ARM outside of the exceptions for Microsoft's own applications. I don't think we have details if the new plans include allow developers to cross-compile Win32 apps to ARM, in addition to the x86 emulation.