Live data from Hacker News

DirectX is coming to the Windows Subsystem for Linux

devblogs.microsoft.com

51–60 of 548 posts

Re: DirectX is coming to the Windows Subsystem for Linux

#51
post #35
post #16

I remember when DirectX was a huge obstacle to porting games to Linux. This feels like a great, great victory for Linux to me!

> This feels like a great, great victory for Linux to me! Why? This is not DirectX on the Linux desktop, it is DirectX for WSL. This means that code written for this will NOT function on desktop Linux. Additionally, support for DirectX for WSL is support not spent on Vulkan and OpenGL.

[deleted]

Re: DirectX is coming to the Windows Subsystem for Linux

#52
"There is no intent for anyone in the Linux world to start coding for the DX12 API."

https://lkml.org/lkml/2020/5/19/1139

"This is a driver that connects a binary blob interface in the Windows kernel drivers to a binary blob that you run inside a Linux guest."

https://lkml.org/lkml/2020/5/19/1288

Re: DirectX is coming to the Windows Subsystem for Linux

#54
The title is misleading.

This isn't DirectX on Linux. This is DirectX API access for WSL exclusively. It will lock ML projects into Windows/WSL for the price of access to the DirectX API and at the expense of development of other projects like Vulkan for native Linux.

Re: DirectX is coming to the Windows Subsystem for Linux

#55
post #6

...and extend. I'm sure this architecture was easier for MS but it opens the door to code that runs on WSL2 that doesn't run on regular Linux.

In a previous life I wrote code that only ran in Cygwin, it depended on a dummy networking driver to talk to the WinCE core of a sonogram machine.

Running Windows VMs as kernels for Cygwin environments felt less weird than most modern container architectures.

Re: DirectX is coming to the Windows Subsystem for Linux

#56
post #44
post #6

...and extend. I'm sure this architecture was easier for MS but it opens the door to code that runs on WSL2 that doesn't run on regular Linux.

It doesn't just open the door, it absolutely requires it.

How? For example code that uses CUDA on Linux, calls the GPU CUDA driver, which passes it on to the Windows part of the interface. How does that require user code that doesn't run on normal Linux to take advantage of this?

Re: DirectX is coming to the Windows Subsystem for Linux

#57
post #48
post #36

Earlier quoted context omitted.

No, this is only an extension of WSL, it will not impact desktop Linux.

Thank you. In the meantime I also noticed the following comment from Dave Airlie on LKML [1]: > This is a driver that connects a binary blob interface in the Windows kernel drivers to a binary blob that you run inside a Linux guest. It's a binary transport between two binary pieces. [...] I can see why it might be nice to have this upstream, but I don't forsee any other Linux distributor ever enabling it or having to…

He's pretty against it on a number of fronts.

That being said I don't see why distros like Ubuntu that allow non free code wouldn't ship with it out of the box. They already support Nvidia binary drivers anyway, so why wouldn't they support a transport bridge that'd let people use them on WSL too?

Also, he notices that it's intended to be more than a bridge in the future, as they're already working on integrating it with the presentation layer on Linux.

Re: DirectX is coming to the Windows Subsystem for Linux

#58
post #6

...and extend. I'm sure this architecture was easier for MS but it opens the door to code that runs on WSL2 that doesn't run on regular Linux.

> it opens the door to code that runs on WSL2 that doesn't run on regular Linux That's a strange complaint. Would you be happier if this was merged into the mainline kernel instead?

What I mean is imagine an app that supports "Linux" but it only runs on WSL2; it doesn't run on real Linux. That would be bad IMO.

Re: DirectX is coming to the Windows Subsystem for Linux

#59
post #54

The title is misleading. This isn't DirectX on Linux. This is DirectX API access for WSL exclusively. It will lock ML projects into Windows/WSL for the price of access to the DirectX API and at the expense of development of other projects like Vulkan for native Linux.

Not anymore so than they're already locked into CUDA. It's more a WDDM bridge than a strict DirectX bridge.
Post reply on HN