Apple could really speed things up for game development for these new machines by making a new boot camp for Windows ARM and making windows directx drivers for their GPU. But we know they won’t.
I don’t buy that; DX is well documented and there are at least a couple open source “translation” libraries to learn from. You’re right that it’d be a lot of work and even more support headaches, though. It’d be a tough elevator pitch for sure.For Apple Silicon, MS would have to help write the DX drivers. Apple can’t just write it.
I don’t buy that; DX is well documented and there are at least a couple open source “translation” libraries to learn from. You’re right that it’d be a lot of work and even more support headaches, though. It’d be a tough elevator pitch for sure.
Apple’s SoCs support all of the ARMv8 instructions, so MS doesn’t *have* to do anything. ARM Windows would benefit from Apple’s extensions, but it’s not like it would run worse than on whatever vanilla ARM processor. Apple (or a few enterprising OSS fellas, say the Asahi Linux crew plus some Windows fans) could write drivers and it would probably be good.Maybe but I edited the quotes sentence with other issues: namely the changes to Windows kernel to support AS. MS would have to make those. Right now they won’t even sell licenses for standard ARM hardware - which is kind of a necessary first step. It’s why VMWare has said they won’t support Windows even through virtualization.
I don’t buy that; DX is well documented and there are at least a couple open source “translation” libraries to learn from. You’re right that it’d be a lot of work and even more support headaches, though. It’d be a tough elevator pitch for sure.
Apple’s SoCs support all of the ARMv8 instructions, so MS doesn’t *have* to do anything. ARM Windows would benefit from Apple’s extensions, but it’s not like it would run worse than on whatever vanilla ARM processor. Apple (or a few enterprising OSS fellas, say the Asahi Linux crew plus some Windows fans) could write drivers and it would probably be good.
Craig Federighi even stated that it would be up to Microsoft to support the M1 hardware but that it was possible because the boot loader is open, just like the Asahi Linux project.There is no doubt that Apple could implement the drivers necessary to run Windows natively. There is even less doubt that they won’t do that. It’s a lot of work with zero payout for Apple. They don’t even want to support Vulkan in macOS.
Windows would need kernel modifications just to boot on Apple Silicon. A lot of low level stuff is just different: interrupts, between CPU communication… alternative would be Apple writing a low level hypervisor that „pretends“ that this is a regular ARM PC, aka Bootcamp 2.0, but again, a lot of tricky work with zero payout.
There is no doubt that Apple could implement the drivers necessary to run Windows natively. There is even less doubt that they won’t do that. It’s a lot of work with zero payout for Apple. They don’t even want to support Vulkan in macOS.
Windows would need kernel modifications just to boot on Apple Silicon. A lot of low level stuff is just different: interrupts, between CPU communication… alternative would be Apple writing a low level hypervisor that „pretends“ that this is a regular ARM PC, aka Bootcamp 2.0, but again, a lot of tricky work with zero payout.
Craig Federighi even stated that it would be up to Microsoft to support the M1 hardware but that it was possible because the boot loader is open, just like the Asahi Linux project.
Craig Federighi even stated that it would be up to Microsoft to support the M1 hardware but that it was possible because the boot loader is open, just like the Asahi Linux project.
This is all why I stand by the notion that this would have to be a deal between the two companies and while I can imagine reasons for each to do so, at the moment I don’t see it happening. MS attitude is that WoA is OEM-only and Apple’s is that we’ll support boot loading but after that you’re on your own.
Virtualization is the simplest and most effective path forward. Frankly, it would help if Apple introduced some "compatibility support" features for Metal that would make it easier to map DX and VK idiosyncrasies to Metal.
Federighi's statement was taken widely out of context. He was referring to virtualization. Apple does open native boot to third-party implementations, but they do not release any documentation which makes it worthless for production use. Asahi Linux can spend time reverse-engineering Apple hardware and patching the kernel because they are passionate idealists. Microsoft will do no such thing.
Sure I agree with that, but even virtualization is kind of hamstrung by MS insistence that WoA is not for sale. ? Obviously it still works and you can do it, but it makes it feel … not so great.
To be fair taken out of context with reason. If I remember right, the question was pretty geared towards boot camp even if the answer was not so I understand why people think they were talking bare metal support (though as you say that is a little unreasonable to expect of MS without direct support from Apple.)
Well, you know, if that's MS official position, then taking about the possibility of native boot makes even less sense. Yeah, it's a ... suboptimal situation.
That's from Gruber's interview, right? They discuss hypervisors just afterwards where Federighi says out direct that they are not talking about native boot.
The one got people excited was the Arstechnica interview who botched it up:
“We are giddy”—interviewing Apple about its Mac silicon revolution
Craig Federighi, Johny Srouji, and Greg Joswiak tell us the Apple Silicon story.arstechnica.com
And the macrumors copied their version:
Craig Federighi: Native Windows on M1 Macs is 'Really up to Microsoft'
Following the release of the M1 Macs Apple executives have been doing interviews with a range of publications, and today, Ars Technica published...www.macrumors.com
That’s why people still think he was discussing bare metal. Because it was reported that way in a lot of outfits.
Ah, I see. The article did say "as to native support". Given Apple's stance on the matter and the fact that their hardware is proprietary, and considering what they said in other interviews, I believe that this article misquoted Federighi.
Since you can't play them unplugged, money wise it's better to buy an Xbox for your a MS kind of guy.That's great and all but who's going to spend $3500+ along with cost of Parallels and Crossover subscriptions and a lot of trial and error time just to play a limited number of older games so they can say they get 1.5 hours or less unplugged and unthrottled? How realistic is that vs buying a Lenovo Legion with 3060 or even 3070 for $1400 or less when on sale that can play all games including recent titles, faster with better quality plugged in and seamless without loss hair?
It's much much easier to get a gaming laptop vs. a Xbox Series X. (Sorry, the ubiquitous Series S is really last gen specs masquerading as current gen hardware)Since you can't play them unplugged, money wise it's better to buy an Xbox for your a MS kind of guy.
This is a bit misleading.Craig Federighi even stated that it would be up to Microsoft to support the M1 hardware but that it was possible because the boot loader is open, just like the Asahi Linux project.
Most of the cost burden would be with Microsoft. In the 15 years of Intel Macs has there been substantial demand for Windows on the Mac?This is a bit misleading.
Yes, Microsoft could support Windows 11 on ARM for the M1 chips. The issue is that would require work on both ends to get it functioning. Of biggest note, the M1 chips do not support UEFI and ACPI, both of which are required for Windows 11.
Is it possible that Microsoft would remove those, but it's also possible that every more game dev studios code directly for Metal and the M1 chips. It remains to be seen what will happen, and I'm not exactly holding my breath. BOTH sides would have to make concessions, and I'm honestly not sure it'll happen. It's much more complicated than Craig would have you believe.