Wine 3.0 Still Expected Around EOY With D3D11; Wayland & D3D12 On Roadmap

[Brane215]

He said more or less nothing. Work on wayland suport has started and will problably not be finished in 3.0. So ? What does that mean ? Will it take a few months or another 10 years ?
Are problems deemed solvable within winehq or do they need coordination with other projects etc ?

[moilami]

Has been a long way since hoping Baldur's Gate II would work with Wine

[Dukenukemx]

So any word on Gallium Nine and D3D to Vulkan?

[DMJC]

All I want is proper DirectDraw/DirectX 6 support...

[duby229]

Or maybe it's time for operating systems like MacOS and linux and BSD to impliment windows API's natively. And for those that choose not to, too fucking bad. Idiots. That way wine can -actually- be a wrapper and not an emulator. Because that's -exactly- what it is.

It should have been started 15 or more years ago, and probably -would- have started then if not for wine's flat out lies. Wine still has horrible compatibility and as long as they continue designing it to be such a high level emulator it never ever will.

[bobwya]

Wine on Wayland ... confirmed

Direct X12->Vulkan translation layer ... confirmed

[dragon321]

Or maybe it's time for operating systems like MacOS and linux and BSD to impliment windows API's natively. And for those that choose not to, too fucking bad. Idiots. That way wine can -actually- be a wrapper and not an emulator. Because that's -exactly- what it is.

It should have been started 15 or more years ago, and probably -would- have started then if not for wine's flat out lies. Wine still has horrible compatibility and as long as they continue designing it to be such a high level emulator it never ever will.

No, Wine isn't emulator. Wine is compatibility layer. There isn't any emulation in this. Windows process'es in Wine are equal to Linux/macOS/BSD native process'es. The only difference is that there isn't run native, but it's translated to native API's. According to this You can call Java Virtual Machine or .Net Runtime "emulators". Because they translate before run too There isn't any sense with merging Wine to kernel, if userland process can do same thing. If You want Windows API in kernel just install Windows. If You want free kernel compatible with Windows kernel, try ReactOS.

Do You really thing that userland nature of Wine makes compatibility bad? Lol. If You want better compatibility just ask Microsoft for Windows source code. Because this is the reason why compatibility is bad - closed source and no documentation, not userland nature of Wine. Moving Wine to kernel isn't solution for that and this would make Wine run on only one platform. This is stupid idea with completely no sense.

Next time before You call somebody "idiot", learn something about situation. This is funny when somebody knows nothing about project and tries to "improve" it with stupid and nonsense ideas/

[mbello]

I guess you didn't get the memo. Windows is the one needing a compatible API with Linux and they have already built it, code is already out to the public.
Way way more code is developed to the web and to mobile devices these days. The cloud is ran on Linux and Android (Linux) is the most popular mobile platform, second place is iOS so Windows has lost already.

Now is not the time when Linux and Mac need to go compatible with Windows. Now is the time when the ecosystem has become heterogeneous and we all need to rely on open standards. Proprietary lock-in is out, open standards are in.

Windows in 2017 is what BlackBerry was in 2007, by far the dominant platform but already fatally wounded.

Or maybe it's time for operating systems like MacOS and linux and BSD to impliment windows API's natively. And for those that choose not to, too fucking bad. Idiots. That way wine can -actually- be a wrapper and not an emulator. Because that's -exactly- what it is.

It should have been started 15 or more years ago, and probably -would- have started then if not for wine's flat out lies. Wine still has horrible compatibility and as long as they continue designing it to be such a high level emulator it never ever will.

[duby229]

No, Wine isn't emulator. Wine is compatibility layer. There isn't any emulation in this. Windows process'es in Wine are equal to Linux/macOS/BSD native process'es. The only difference is that there isn't run native, but it's translated to native API's. According to this You can call Java Virtual Machine or .Net Runtime "emulators". Because they translate before run too There isn't any sense with merging Wine to kernel, if userland process can do same thing. If You want Windows API in kernel just install Windows. If You want free kernel compatible with Windows kernel, try ReactOS.

Do You really thing that userland nature of Wine makes compatibility bad? Lol. If You want better compatibility just ask Microsoft for Windows source code. Because this is the reason why compatibility is bad - closed source and no documentation, not userland nature of Wine. Moving Wine to kernel isn't solution for that and this would make Wine run on only one platform. This is stupid idea with completely no sense.

Next time before You call somebody "idiot", learn something about situation. This is funny when somebody knows nothing about project and tries to "improve" it with stupid and nonsense ideas/

What's really funny is when people like you insist they know what they're saying is right, when the real fact is they are wrong. Wine -does- emulate windows behavior, it must because they -cannot- rely on the behavior of native linux libraries. They have no option but to emulate the windows libraries behavior using native libraries that they cannot rely on!

Please try to understand what -emulate- means. Here it is in all of its glory.

https://www.merriam-webster.com/dictionary/emulate

It clearly says "to strive to equal" In this case equal compatibility. They aren't emulating at a low level, they are doing it at the highest level conceivably possible just like retarded morons. If they had bothered to impliment windows API's natively and then simply wrapped them, like their namesake implies, then it -could- rely on the behavior of the natively implemented windows libraries. Then it wouldn't emulate anything, it would truly be a wrapper environment.

[duby229]

I guess you didn't get the memo. Windows is the one needing a compatible API with Linux and they have already built it, code is already out to the public.
Way way more code is developed to the web and to mobile devices these days. The cloud is ran on Linux and Android (Linux) is the most popular mobile platform, second place is iOS so Windows has lost already.

Now is not the time when Linux and Mac need to go compatible with Windows. Now is the time when the ecosystem has become heterogeneous and we all need to rely on open standards. Proprietary lock-in is out, open standards are in.

Windows in 2017 is what BlackBerry was in 2007, by far the dominant platform but already fatally wounded.

Which is gonna give windows huge unfair advantage! It'll be able to reliably run linux apps, and because of wine, linux still won't be able to reliably run windows apps. That situation sucks ass and is no way a good thing at all!