If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
No announcement yet.
Microsoft Begins Landing Changes For Cross-Platform Support With Their Mesa D3D12 Code
Its really not. MS forked Mesa would be used by microsoft and no one else. They'd have to do the extra work of porting upstream patches or their patches every new version and would be a huuge maintenance burden of microsoft.
No one, and I mean no one, is going to use the microsoft fork because they aren't providing ANYTHING for anyone else.
It's not, because at least if they fork it, it's their issue. Their maintainer. Their pulls and syncing. Them, not Mesa. Instead, Mesa people are handling Microsuck's garbage instead of Microsuck themselves.
As long as they're okay with it/getting paid to, it's fine. But it's basically a cancerous tumor. How many others would be accepted like this by the maintainers before they said no? Why is it okay for Microsoft to do this crap with no benefit to anyone but themselves?
Microsuck needs to maintain Microsucks crap, not Mesa.
The very idea of using native applications with DirectX support in Linux is initially bad, because it is not cross-platform.
Much more useful from Vulkan, OpenGL, OpenCL.
It's not, because at least if they fork it, it's their issue. Their maintainer. Their pulls and syncing. Them, not Mesa. Instead, Mesa people are handling Microsuck's garbage instead of Microsuck themselves.
As long as they're okay with it/getting paid to, it's fine. But it's basically a cancerous tumor. How many others would be accepted like this by the maintainers before they said no? Why is it okay for Microsoft to do this crap with no benefit to anyone but themselves?
Microsuck needs to maintain Microsucks crap, not Mesa.
Leave a comment: