Support us on Patreon
PayPalStadia is something we don't really talk about here too much now, as Google has let it slide considerably from the original aim but it's still going and it seems Google still has some interesting plans for it.
There's an upcoming Google For Games Dev Summit on March 15, which includes Android and Stadia. For the Stadia service that runs on Debian Linux, Google has a few talks including "Play Testing Made Easy on Stadia", "Stadia Adventures in slow server code on Unity" and "Profiling on Stadia" but the perhaps bigger one is titled "How to write a Windows emulator for Linux from scratch?" that notes:
Detailed overview of the technology behind Google's solution for running unmodified Windows games on Stadia. This is a deep technical walkthrough of some of the core concepts with the goal to allow curious programmers to better understand such technologies and potentially to build their own.
We don't know yet if it will be open source but the bigger question perhaps is why they didn't go with all the existing code that has already proven itself? We are of course talking about Wine / Proton, DXVK and VKD3D-Proton which powers Windows games on Linux desktop and the Steam Deck. It's already shown to have great performance.
It's an obvious move for Stadia though to help increase the game library, the same reason Valve created Proton from Wine to bring more games to Linux systems. We'll be taking a look over the talk on March 15 and will make some notes for you.
Article taken from GamingOnLinux.com.
Quoting: ShmerlQuoting: EikeNobody said anything about hardware except you.
Not true. All those who got hung up on "Wine is not an emulator" were busy defining emulator as something that has to emulate CPU architecture and such. While the meaning of the word emulate never had to be limited to what they wanted.
You've got the whole thread at your disposal to cite all those. Nobody here was defining it this way, and you ignored - and are still ignoring - all arguments that actually were given.
Wine is not a Windows emulator, because it does not provide a Windows environment: it does not allow using of Windows drivers, does not emulate devices, or network interfaces that would normally be found on a Windows system, etc. That is why most software that interacts with hardware will not work in Wine. Also why anticheat and DRM software does not work.
It's much more like what Mono is to .NET, or like Pipewire to Pulseaudio, or like FNA to XNA, or DXVK to DirectX, etc. They implement the same API, which allows to use them interchangeably without modifying the clients. At least in theory you could write a native Linux application against Wine API and there would be no emulation involved.
But API itself is not quite enough to trick actual Windows applications. That is why Wine does indeed emulate parts of Windows, like filesystem structure and drive names. And the Wineserver process provides roughly the same services as a Windows kernel would.
Wine is largely not an emulator, but has some traits of an emulator. Just enough emulation sprinkled on top to make us nerds worldwide argue over nomenclature.
Quoting: EikeYou've got the whole thread at your disposal to cite all those. Nobody here was defining it this way,
And I'm not talking about people here, but about those who were originally annoyed at Wine calling itself an emulator, causing it to be rebranded as "not an emulator". So not sure what your point is exactly. None of these people are here I presume.
Quoting: ShmerlQuoting: EikeYou've got the whole thread at your disposal to cite all those. Nobody here was defining it this way,
And I'm not talking about people here, but about those who were originally annoyed at Wine calling itself an emulator, causing it to be rebranded as "not an emulator". So not sure what your point is exactly. None of these people are here I presume.
You've been explicitly talking about the present:
Quoting: ShmerlWine emulates Windows, so it is an emulator of it. But some can't understand the term except in the context of emulating hardware, so they probably insisted that "Wine is not an emulator [of hardware]".
Windows consists of a lot of things, including but absolutely not limited to...
[ ] API
[ ] ABI
[ ] Scheduler
[ ] Memory manager
[ ] Kernel
[ ] File handling
[ ] Drivers
[ ] User interface
[ ] ... you name it.
Most of this is not - at all - handled by WINE, and therefore, WINE is not a Windows emulator, and will never be.
Last edited by Eike on 11 March 2022 at 9:00 pm UTC
Emulation can mean emulating software. Those who don't like this or don't get it can move along. Arguing with them is a complete waste of time.
Last edited by Shmerl on 11 March 2022 at 9:03 pm UTC
Quoting: LinasIt's much more like what Mono is to .NET, or like Pipewire to Pulseaudio, or like FNA to XNA, or DXVK to DirectX, etc. They implement the same API, which allows to use them interchangeably without modifying the clients. At least in theory you could write a native Linux application against Wine API and there would be no emulation involved.
But API itself is not quite enough to trick actual Windows applications.
To deviate even further: I found news group postings from '93 where they call it "WINDOWS API emulator" - but isn't it technically the ABI, not the API, they're... whatevertheyredoingwithit?
Quoting: ShmerlEmulation can mean emulating software. Those who don't like this or don't get it can move along. Arguing with them is a complete waste of time.
This is still nothing anybody here has been saying around here. That's why the discussion doesn't work. Arguing would need to deal with the actual arguments given, which you're not doing today.
Again, for your reading pleasure:
Windows consists of a lot of things, including but absolutely not limited to...
[ ] API
[ ] ABI
[ ] Scheduler
[ ] Memory manager
[ ] Kernel
[ ] File handling
[ ] Drivers
[ ] User interface
[ ] ... you name it.
Most of this is not - at all - handled by WINE, and therefore, WINE is not a Windows emulator, and will never be.
(You see? Nothing about hardware, nothing about there would be no possibility to emulate software.)
Last edited by Eike on 11 March 2022 at 9:11 pm UTC
Last edited by Shmerl on 11 March 2022 at 9:12 pm UTC
Quoting: ShmerlGood, then what are you even arguing about? If discussion doesn't work for you, don't engage in discussion :)
It work's as soon as you're going to read, understand and answer my argument. WINE cannot be a Windows emulator because it doesn't intent to emulate Windows, which is way more than an API/ABI.
See more from me