3 ms·

> I’d love them to be, but unfortunately there’re technical reasons for that. Both depend on too many Windows components. WinForms is really a thin wrapper arou

> I’d love them to be, but unfortunately there’re technical reasons for that. Both depend on too many Windows components. WinForms is really a thin wrapper around Win32 windows and GDI+. WPF relies heavily on DirectX 9. And yet somehow Mono is able to (mostly) emulate WinForms, while Wine can (mostly) emulate D3D9. And MS can't (at least) throw their weight behind that, rather than wasting time on WSL? > Again, there’re technical reasons. For the same reasons Apple is pushing Metal, and Khronos is pushing Vulkan, all 3 are conceptually quite similar. So why aren't Microsoft (and Apple) pushing Vulkan as well, rather than their own "quite similar" APIs?

Const-me 9y ago
> MS can't (at least) throw their weight behind that, rather than wasting time on WSL? I don’t know the answer to that, I’m unrelated to MS, not even on the same continent. But I have an idea why. Because outside Android, Linux GPU stack is a mess. Maybe Vulkan will fix it, but it’s not happened yet. I’m just not sure it’s possible to build a good product on top of that. But they sure can build a single cross-platform GUI library for Windows, OSX, and mobile platforms. And I hope they will. > why aren't Microsoft (and Apple) pushing Vulkan as well, rather than their own "quite similar" APIs? Apple released Metal in 2014. MS released DX12 in 2015. Vulkan was first announced in 2015, and they released 1.0 version of the spec only in 2016. That’s why.