In this episode of Zed Decoded, Thorsten talks to Mikayla, who's been leading the effort to Zed working on Linux, about the Zed's Linux version and how it's taking shape
Is there any particular problem with MoltenVK? As I see it, it’s by far the best solution for cross platform software on macOS in need of graphical hardware acceleration.
There’s nothing wrong with the software itself. It works great for what it does. On the other hand, it’s a compatibility layer, which always increases friction between things a little. I think the best use for this is running legacy software.
There aren’t many alternatives. Maybe in the future, we’ll see graphics API abstraction libraries like wgpu get used more. This gives developers a single API which can use DirectX on Windows, Vulkan on Linux, or Metal on macOS. This could allow support for entirely new graphics APIs without developers using it having to do anything.
Of course, that’s my opinion. People can build their software how they like.
Is there any particular problem with MoltenVK? As I see it, it’s by far the best solution for cross platform software on macOS in need of graphical hardware acceleration.
There’s nothing wrong with the software itself. It works great for what it does. On the other hand, it’s a compatibility layer, which always increases friction between things a little. I think the best use for this is running legacy software.
There aren’t many alternatives. Maybe in the future, we’ll see graphics API abstraction libraries like wgpu get used more. This gives developers a single API which can use DirectX on Windows, Vulkan on Linux, or Metal on macOS. This could allow support for entirely new graphics APIs without developers using it having to do anything.
Of course, that’s my opinion. People can build their software how they like.