And nothing wrong with that, the classic Win32 API is actually quite decent, especially the small subset needed for games. And it has the incredible advantage that it doesn't change since Microsoft doesn't care about Windows anymore ;)
The original comment by Linus was that Valve would not accept the current state of things where to distribute a program on Linux you need to create a different package for every single distro. Which is true, Steam with Proton has pushed a single stable platform where you can publish a single build and it works everywhere. In desktop mode of SteamOS everything is installed through Flatpak.
...by emulating WinAPI
And nothing wrong with that, the classic Win32 API is actually quite decent, especially the small subset needed for games. And it has the incredible advantage that it doesn't change since Microsoft doesn't care about Windows anymore ;)
That's not why it doesn't change.
The original comment by Linus was that Valve would not accept the current state of things where to distribute a program on Linux you need to create a different package for every single distro. Which is true, Steam with Proton has pushed a single stable platform where you can publish a single build and it works everywhere. In desktop mode of SteamOS everything is installed through Flatpak.
Heh, who cares. I can play games and my OS doesn’t spy on me.
There is always Android ABI but kernel developers still think android is a calamity rather than biggest Linux success story ever...
The funny thing would be for Wine to then extend the WinAPI, and software beginning to use that extension.
Microsoft: embrace, extend… no, not like that! Stop!
Reverse EEE?
Embrace, extend…
By _embracing_ the WinAPI!
Sometimes you have to walk with the devil to do good deeds.
I thought it was a translation layer? Not emulation right?