Comments on: Full Windows 10 on ARM 64bit 10nm Qualcomm Snapdragon 835 https://armdevices.net/2017/06/02/full-windows-10-on-arm-64bit-10nm-qualcomm-snapdragon-835/ New video posted every 8 hours, forever Sun, 04 Jun 2017 09:54:00 +0000 hourly 1 https://wordpress.org/?v=7.0.2 By: davidlt https://armdevices.net/2017/06/02/full-windows-10-on-arm-64bit-10nm-qualcomm-snapdragon-835/comment-page-1/#comment-18049 Sun, 04 Jun 2017 09:54:00 +0000 http://138.2.152.197/?p=135234#comment-18049 In reply to Travis Siegel.

They did what you explained. UWP applications now container target for multiple architectures (x86, x86_64, aarch64 (aka arm64). Supporting legacy applications are also required for many years until majority applications are built for multiple architectures. Note, that pure .NET based application had no troubles running even on Surface RT.

Remember that first time you launch application it will be translated from x86 (and later x86_64) to aarch64 and result will be saved to the disk. Next time you are running the native code without emulating anything. They did also other things to make x86 on aarch64 run fast.

E.g., Microsoft Office will be native once launched.

]]> By: Travis Siegel https://armdevices.net/2017/06/02/full-windows-10-on-arm-64bit-10nm-qualcomm-snapdragon-835/comment-page-1/#comment-18048 Sun, 04 Jun 2017 00:12:00 +0000 http://138.2.152.197/?p=135234#comment-18048 MS already has a version of windows that runs on arm (windows IOT). It wouldn’t be difficult for them to finish the job, and make windows run natively on arm, then provide arm as one of the executable types in it’s universal apps (much like apple with ppc, intel32, intel64, and so on). Eventually, most developers would provide arm versions of their programs because of demand. I see no reason to waste cpu cycles emulating something that is already (mostly) ported to native code version. This is a step in the wrong direction in my opinion.

]]>