It's not normally paging, but thermal throttling which involves the machine appearing to 'spin' but it's actually just the kernel keeping the cycles to itself, which typically give you beachballs as a side-effect.
And one tip is to use the right hand side USBC ports for charging, not the left hand ones as for some reason or other they tend to cause the machine to heat up more...
the right hand ones are the only ones that can drive external monitors (on mine anyway). I feel like I'm the only one that has this - I had a MBP 2019 - first batch - and I thought I'd read that one side was different than the other re: power. Power works on both sides, but monitors won't run from the left usb-c ports. but it's not documented anywhere. :/
I don't see any mention of x86_64/AMD64 in the article. I would expect a version of Windows which can't run x86_64 apps to result in a lot of nasty compatibility surprises--it's been awhile since developers had to support 32-bit-only hardware--so I'd expect Microsoft to support it if at all possible.
You're right, the posted Anandtech article does not mention x86_64; however, other prior and recent coverage of this topic does confirm that x86_64 is not supported, such as this Ars Technica article [1] from the same day.
There's no support for x86_64 binaries. Windows 10 is still available in 32-bit editions and almost all apps are still available for 32-bit, so I don't think this is a big issue.
I assume any kernel drivers will need to be compiled for ARM64 though. This might not help corporate adoption--VPN client, 3rd party anti-virus/full disk encryption, etc.
Also one thing that is x86-64 only is WSL, the Windows Subsystem for Linux.
I think most Windows applications which are truly 64-bit only are either too large to run on a machine like this, or likely to be rebuilt for AArch64. For the time being, I think IA-32 support is enough to tide them over, and it has the benefit of being thoroughly out of patent (except some fairly common extensions, like SSE2, which will expire soon).
There's still a lot of Windows devices that run x86 Windows, and new devices still ship with it, mostly low-memory or low-disk-space devices. Thus apps need to support it.
The Intel patents for up to SSE2 should expire soon, and hopefully the AMD64 patents should be licenseable from AMD (if they are interested in that). I would not be surprised if this already emulates up to SSE2, given the likely release date and the fact that recent versions of MSVC already enable /arch:SSE2 by default.
> I would not be surprised if this already emulates up to SSE2, given the likely release date.
Yeah, even if they could be sued, they could settle for a couple years damages max, or quite possibly win, since they're doing DBT (no different from QEMU or loads of other x86 + SSE2 emulators).
though it's worth remembering that QEMU developers do not have the deep pockets that MS has -- and it is the depth of the pockets, rather than the (alleged) violation that drives law suits and threats.
