Games run faster on SteamOS than Windows 11, Ars testing finds
1–10 of 285 posts
Re: Games run faster on SteamOS than Windows 11, Ars testing finds
#2Might be unfair to call Proton a "translation layer" because the Win32 API is not defined in terms of system calls but rather a set of functions exported from a DLL.
Proton supplies a DLL that implements the Win32 API using Linux syscalls. Windows supplies a DLL that implements that Win32 API using Windows syscalls that you're not really supposed to use directly.
Re: Games run faster on SteamOS than Windows 11, Ars testing finds
#3Might be unfair to call Proton a "translation layer" because the Win32 API is not defined in terms of system calls but rather a set of functions exported from a DLL. Proton supplies a DLL that implements the Win32 API using Linux syscalls. Windows supplies a DLL that implements that Win32 API using Windows syscalls that you're not really supposed to use directly.
https://www.winehq.org/ calls it a compatibility layer that translates calls on the fly.
so 'translation layer' is not that unfair.
Re: Games run faster on SteamOS than Windows 11, Ars testing finds
#4Borderlands 3? Homeworld 3? Who chose these games? Why not just use the current top 10 on Steam atm?
Re: Games run faster on SteamOS than Windows 11, Ars testing finds
#5Borderlands 3? Homeworld 3? Who chose these games? Why not just use the current top 10 on Steam atm?
[deleted]
Re: Games run faster on SteamOS than Windows 11, Ars testing finds
#6Borderlands 3? Homeworld 3? Who chose these games? Why not just use the current top 10 on Steam atm?
"To test the performance impact of this operating system choice, we started with the SteamOS version of the Legion Go S (provided by Lenovo) and tested five high-end 3D games released in the last five years using built-in benchmarking tools..."
those games come with benchmark tools
Re: Games run faster on SteamOS than Windows 11, Ars testing finds
#7Might be unfair to call Proton a "translation layer" because the Win32 API is not defined in terms of system calls but rather a set of functions exported from a DLL. Proton supplies a DLL that implements the Win32 API using Linux syscalls. Windows supplies a DLL that implements that Win32 API using Windows syscalls that you're not really supposed to use directly.
https://www.winehq.org/ calls it a compatibility layer that translates calls on the fly. so 'translation layer' is not that unfair.
If it is forwarding to libc() as opposed to syscalls directly than maybe ‘translation’ is fair.
Re: Games run faster on SteamOS than Windows 11, Ars testing finds
#8Seems more like a test of the hardware than Windows 11 and SteamOS since they ran into driver issues immediately. Not to mention those frame rates are terrible across the board. Just not very good hardware.
Re: Games run faster on SteamOS than Windows 11, Ars testing finds
#9Might be unfair to call Proton a "translation layer" because the Win32 API is not defined in terms of system calls but rather a set of functions exported from a DLL. Proton supplies a DLL that implements the Win32 API using Linux syscalls. Windows supplies a DLL that implements that Win32 API using Windows syscalls that you're not really supposed to use directly.
Wine is translating Windows ABIs (not APIs) into underlying Linux OS and userland. Translation simply means that normally Windows ABIs are meant to be used on Windows, they aren't native on Linux.
Re: Games run faster on SteamOS than Windows 11, Ars testing finds
#10Earlier quoted context omitted.
https://www.winehq.org/ calls it a compatibility layer that translates calls on the fly. so 'translation layer' is not that unfair.
If it is forwarding to libc() as opposed to syscalls directly than maybe ‘translation’ is fair.
I think that's how it started out, and also how a lot of developers still conceptualize it. Wine has had to massively expand that scope to reach the maturity it has now. I think it's kind of straddling the line between "Implementation" and "translation".
Philosophically its still a translation layer though. It doesn't really care about correctness if the no apps depend on it. Success is in meaningfully running client software. The implementation of the Windows Libraries are just a way to get there.