[Rhedox]

> This is also a triumph for open source imho because wine is now receiving patches for macOS directly, and it’s a symbiotic relationship that hopefully grows.

I wish. Unfortunately the MetalD3D is proprietary under a very restrictive license. The rest is just Wine code written by Codeweavers.

[simondotau]

I don't understand your pessimism. If Apple finds and fixes a gap in Wine's coverage/compatibility, those changes will necessarily be open source. Quite simply, any work which Apple does that could be useful to the wine project will be open source.

Obviously it would be nice if MetalD3D was also released under a better license, but it's hardly as though this omission is a big loss to the wine project.

[meibo]

Apple did not upstream anything to Wine here. They just use CodeWeavers code for macOS support, plus their own changes, and released a 20k line diff to be compliant.

The license to their translation layer(which is closed source) is very restrictive and basically only allows use for evaluation purposes.

[veave]

This is not really important since Metal is Apple-exclusive, right? It's not like it can be used on Linux

[rollcat]

It's still not a great thing to do. Apple used to contribute a lot more, even if some of their stuff was exclusive to their platform. https://opensource.apple.com

[pzo]

But it would be useful for OSS to do translation from Metal to DirectX - Apple probasbly doesn't want that.

[threeseed]

> MetalD3D is proprietary under a very restrictive license

Can you explain this. Game Porting Toolkit code is LGPL the same as Wine.

[microtonal]

The Game Porting Toolkit contains a proprietary (143 MiB) D3DMetal framework that directly translates the Direct3D calls to Metal. They don't use the Direct3D --Wine--> Vulkan --MoltenVK--> Metal path that opensource Wine/CrossOver Wine uses.