Legacy game source releases unlock serious porting work
EA's GPL v3 release of Command and Conquer Generals source code has resulted in something genuinely impressive: native builds running on macOS, iOS, and iPadOS, via a render pipeline that runs DirectX 8 through DXVK, then Vulkan, then MoltenVK, then Metal. The person who did the iOS port documented the full chain, and the community immediately understood the broader implication: Apple's insistence on Metal instead of native Vulkan support forces every ported game through an absurdly long translation chain.
The thread is partly a celebration of what is possible with open source game code, and partly a pointed critique of Apple's graphics platform strategy. Multiple commenters note that native Vulkan drivers on Apple hardware would eliminate multiple translation layers and likely improve performance and stability substantially.
For builders, the more interesting signal is about the methodology. The combination of open source releases, modern translation layers, and a small amount of platform-specific work can bring decade-old games to entirely new platforms. The same playbook applies to any legacy software with a source release.
So what?
If you are working on game or software preservation, or building tools for legacy codebases, this is a proof of concept that the translation layer approach works at a real level of complexity. For anyone shipping on Apple platforms, the Vulkan gap is a genuine engineering cost that Apple shows no sign of closing.