3 ms·
This is not like Universal 2 on Apple's transition, where you can have x64 and ARM versions of the program in the same binary (a "fat" binary). In Universal 2,
by gjsman-1000 5y ago
This is not like Universal 2 on Apple's transition, where you can have x64 and ARM versions of the program in the same binary (a "fat" binary). In Universal 2, the app runs as either 100% Intel or 100% ARM, depending on platform.
Instead, what ARM64EC is, is that you can put some ARM code inside a normally x64 binary and ship that to ARM customers like Surface Pro X users. ARM64EC doesn't run on Intel. It's just meant to speed up the porting effort of Intel programs to ARM because you don't need to make everything ARM, just some of it, to go. The Intel bits will be translated using Microsoft's slower-than-Rosetta-2-on-already-slow-hardware translator.
How many people will use this? Considering how successful Windows on ARM has been, coupled with how apathetic most Windows developers are... I give it a low chance, but who knows?
- gjsman-1000 5y agoMicrosoft's biggest problem, IMHO, is the question why on earth a developer would give a rip about supporting Windows on ARM. It's not like Apple, who said that they were going full ARM on all devices, get on board or run 30% slower than you could, and we won't have that translator forever. The investment to support Apple ARM is obvious in how it pays off. Whereas, this? You're looking at how few people have Snapdragon devices, the (by comparison to M1) truly lethargic performance, slow translation, and the fact that your x64 binaries will still work with the translator. What's the business case for adding ARM support? Almost nobody uses it, and those that do don't strictly-speaking need it for your app to work. The only reason Microsoft has really given for supporting ARM is that you'll do it out of the mercy of your heart for those few ARM users, in the hopes that you'll help build their ARM platform for them. Tough sell.
- ripley12 5y agoI mostly agree that that's the current state of things, but I'm a little more optimistic about the future. The software support for ARM in Windows has taken big leaps and bounds in the last ~6 months; this, the more general x64 emulation, Office, WPF, and probably many others that I'm forgetting. Hardware-wise, we're finally getting a cheap ARM developer kit and we're seeing some very cheap ARM laptops like the Galaxy Book Go. The whole thing's frustratingly slow compared to Apple's transition, but I would not be surprised if ARM is a sizeable chunk of new Windows machines a few years from now.
- gjsman-1000 5y agoI would hope, but not to spoil your hope, but I'm less optimistic. The cheap hardware development kit comes with a Qualcomm Snapdragon 7c. For a development kit, that chip is a joke. It's slower than almost every Windows on ARM laptop you can buy right now, which already aren't known for having good performance. It also comes with only 4GB of RAM and 64GB of storage, hardly enough to even put Visual Studio on it. Microsoft's idea is that you'll only remote-deploy to it for testing because it's not powerful enough to actually do most programming on it. Compared to the $499 Apple Developer Kit which gave you an A12Z, 16GB of RAM and a 512GB SSD... this thing better be, what, $200 at most? It's hardly a development kit if you can't actually develop on it. You also need to remember that Microsoft and Intel's fates are bound together. Intel can put up with Microsoft's affairs and flirtations, but if it ever started getting serious, Intel won't permit it to ever get to even minor threat level.
- ripley12 5y agoVS doesn't currently run on ARM (which sucks, but that's definitely a very high priority for the team; I suspect the recent 64-bit migration is setting the stage for ARM support), so there isn't much point in speccing it to run VS. Agreed that remote development/debugging is not ideal.
- gjsman-1000 5y agoLike I said though about Intel making sure it never becomes a viable threat: https://arstechnica.com/information-technology/2017/06/intel-fires-warning-shots-at-microsoft-claims-x86-emulation-is-a-patent-minefield/ https://arstechnica.com/information-technology/2017/06/intel...
- my123 5y agoVisual Studio ran on Windows on Arm64 since the very beginning, it had broken local debugging for quite a while though... (and of course, doesn't run natively but under binary translation) Officially though, it is not considered as supported.
- 5y ago
- fomine3 5y agoI don't know why you criticize this improvement by saying "but who buy ARM Windows". Their improvement is in progress to sell more ARM Windows devices in the future.
- trynumber9 5y agoWhy is their translator slower than Rosetta 2? What would the technical reasons be?
- gjsman-1000 5y agoThere are a few reasons. To put it simply, Rosetta 2 is a much more technically advanced translator. 1. It came out with 64-bit support right out the gate when Microsoft had spent over 2 years on their translator only supporting 32-bit apps, and only just recently rolled out 64-bit support for translation. 2. Unlike Microsoft's translator, Rosetta 2 scans the file ahead of time and essentially creates a small "map" of the binary to help speed things up. This results in a ~15-20 second delay you open an app in Rosetta 2 for the first time, but much faster performance afterward, while Microsoft's translator doesn't do any of this pre-mapping and has no idea what's coming next. 3. Apple's M1 SoC implements many "shortcuts" within the hardware, such as having native ability to remap Intel memory ordering. This means Rosetta 2 doesn't even have to convert x86 to ARM fully, but instead can convert x86 binaries into a hybrid of x86 and ARM together and can skip steps like memory reordering that Microsoft's translator has to do. Some Windows fans initially said that comparing Microsoft's emulator to Rosetta 2 was unfair because Rosetta 2 "is cheating." Of course, this line of reasoning didn't last long because any cheats to get to the same end results are fair game.
- neogodless 5y ago> Rosetta 2 doesn't even have to convert ARM to x86 fully Think this is just a typo - you meant the other direction?
- gjsman-1000 5y agoFixed. I meant x86 to ARM.
- aseipp 5y ago> This means Rosetta 2 doesn't even have to convert x86 to ARM fully, but instead can convert x86 binaries into a hybrid of x86 and ARM together and can skip steps like memory reordering that Microsoft's translator has to do. I mean, there's no real "hybrid" thing going on at all, it's just a matter of what instructions get emitted by the compiler to match the externally observable semantics. In fact are already ARM platforms that use sequential consistency (TSO) for the memory model besides the M1; Nvidia's Jetson platforms are one such example, and a Rosetta-like translation layer on that platform would be able to take advantage of it all the same. I guess it's just a matter of wordsmithing at the end of the day, though!