wineskin VS MoltenVK

First, you will need to install Homebrew, a command line package manager for macOS. Install it by opening Terminal and running this command:/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" (curl is used to download the installer and /bin/bash tells Terminal how to run it). Hit enter and type in your password if prompted. Once brew is finished installing, paste brew install --no-quarantine gcenx/wine/unofficial-wineskin in and hit enter. If all goes well, an app called Wineskin Winery should show up in your Applications folder. We use --no-quarantine to avoid Gatekeeper because Wineskin isn't code signed with a ($200+) Apple Developer license (I can vouch for Wineskin not being a virus, but you are welcome to look through the source code and come to your own conclusions.) When you open Wineskin Winery, you should see something like this:

https://github.com/KhronosGroup/MoltenVK

Translating between rendering APIs is not really the problem. The GPU design is more different than the API is.

Khronos maintains MoltenVk though, which is "official" as it gets: https://github.com/KhronosGroup/MoltenVK

...technically, Vulkan on Windows is also only supported via 3rd-parties (the GPU vendors), Microsoft doesn't support Vulkan either ;)

MoltenVK implements large parts of Vulkan on top of Metal for Apple systems. It isn't full Vulkan but it makes porting Vulkan games to OS X easier.

That's cool. Maybe I haven't thought enough about this. Let me check it out. FWIW it's this PR that you are referring to I think: https://github.com/KhronosGroup/MoltenVK/pull/1815/

For Metal specifically, they could adopt and contribute to Vulkan and get access to a lot more software. Right now you need to use a compatibility layer, and surely Apple could just support both APIs natively with much lower overhead. But they don't, because it nudges developers to stick to the Apple ecosystem instead of being able to support multiple platforms.

At the moment the most promising thing is MoltenVK (DX12 -> DXVK -> Vulkan -> MoltenVK -> Metal), but the development is not that quick mainly because there aren't tons of developer that works at the same time on the project. It's not actually a Metal related problem at the moment (they have a road map of things that they can be achieved with Metal 3 like Mesh shader and Geometry shader).

What you asked is already existed for at least 8 years. Yeah EIGHT years. It's called "MoltenVK". So far it's the only implementation of Vulkan for macOS. Basically it's a wrapper that runs on top of Metal API.