Hacker News new | past | comments | ask | show | jobs | submit login

How does "someone can install Linux in a VM on Windows"[1] translate into "ajvs won't be able to use Linux anymore"? I don't see how you can make such a claim with a straight face.

[1] WSL is based on Hyper-V virtual machines.




They're already doing it with WSL specific features such as the DirectX driver.

https://devblogs.microsoft.com/directx/directx-heart-linux/


Am I misreading? It looks like they ported the DirectX runtime to Linux under GPL 2.

>> "This is the real and full D3D12 API, no imitations, pretender or reimplementation here… this is the real deal. libd3d12.so is compiled from the same source code as d3d12.dll on Windows but for a Linux target. It offers the same level of functionality and performance (minus virtualization overhead). The only exception is Present(). There is currently no presentation integration with WSL as WSL is a console only experience today. The D3D12 API can be used for offscreen rendering and compute, but there is no swapchain support to copy pixels directly to the screen (yet )."

https://github.com/microsoft/WSL2-Linux-Kernel/tree/e445d061...

https://github.com/microsoft/WSL2-Linux-Kernel/blob/e445d061...

>> "SPDX-License-Identifier: GPL-2.0"

They're also working on supporting all the standard Linux equivalents according to your link. I don't see the third E here.


According to the blog post mentioned earlier[0]:

1. Their kernel implementation is effectively just a paravirtualized proxy to the Windows DX API. So it won't be useful for bare metal users.

2. Only the kernel driver is open source (and presumably that is only thanks to the GPL). The user-mode library is a proprietary component shipped with Windows. I assume this is also DRMed to only work on top of Hyper-V/WSL2, just like many of their VSCode extensions deliberately block usage with unbranded builds (see also: AARD code[1], this isn't exactly new for them).

[0]: https://devblogs.microsoft.com/directx/directx-heart-linux/

[1]: https://en.wikipedia.org/wiki/AARD_code


I agree, it's a good-faith effort on Microsoft's part. I think people have a hard time believing they can operate in a non-adversarial way (which is understandable if you lived through the 90s lol)


Explain how "Microsoft puts a DirectX in WSL" stops you from running Linux in future?

Because it really doesn't seem like it will affect you or what you can do in any way at all.


1. MS adds directx to WSL

2. People write "Linux" apps that require directx

3. Linux technically stays an option but is unable to run apps without NT underneath, and nobody writes plain Linux apps because of market effects

Weak because people could still write apps for just Linux, plausible because convincing people to divert effort to the MS way would work and is classic EEE.


No one in their right mind would right linux apps targeted to run WSL only. Even if they do, it would never capture the market of pure linux. Also any modifications done to linux should be GPLd hence i don’t think thats a problem either.


Your use of "extinguish" describes a situation where you can use exactly what you have now, in exactly the way you're doing now? And the terrible thing which "extinguish" means to you is "future people who might have given me free stuff might not, and it will be Microsoft's fault"? And not only that, but the way MS will "convince people to divert effort" is by making something people want more? And that is somehow terribly unfair?

From Wikipedia:

> "Extinguish: When extensions become a de facto standard because of their dominant market share, they marginalize competitors that do not or cannot support the new extensions." - https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

The current world is that there are programs written for Linux distributions with certain subsystems (audio, window manager, systemd, etc) which don't work on other distributions without those subsystems. People who ignore binary blob video card drivers, etc. A Microsoft Ubuntu with DirectX that only runs in WSL would be just another thing like that. It would be practically no different to "macOS is UNIX but you can't run all macOS programs on other Unixes" which hasn't extinguished Linux or Unix.

Even moreso when people who want to write for DirectX can do so for Windows. Why would those people target DirectX on Linux which only runs on WSL? And if it doesn't only run on WSL, let's say DirectX on Linux works on any Ubuntu and Valve use it for Steam and gaming on Linux becomes massively popular by targetting DirectX for video ... how do you then connect to "nobody writes plain Linux apps because 3D games are an option" and from there to "and now despite being massively more popular, Linux is extinguished and this is bad because even though I can run literally any other distribution and write and run my own software and all previous software, I can no longer be bothered to and that's both bad and Microsoft's fault"?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: