Nah. I mean, there might be some stuff like that, but nowadays, I’d be surprised if feature parity wasn’t 1:1 (or even better, with some open source drivers having features that are removed from official windows drivers…).
The underlying OS is pure garbage, that’s mostly it. Windows will start chugging everywhere with even moderate FS activity: running a background, single-threaded backup process will sometimes make it impossible to click in another window or open a new application. Driver API is not great, you have to jump through hoops to do basic stuff. There are many ways to do the exact same thing, each being more or less efficient than the other. Audio API is so bad, an audio device failing will sometime cause ohter, unrelated, non-audio application to spontaneously combust.
And so on and so on.
On the other hand, the Linux compatibility layer that proton provides do add some overhead in places, but surprisingly, it’s not that much overhead. And it’s not that common (basically, the code runs natively until specific instructions that requires special handling).
Obviously, when you have a better operating base, and very little extra overhead, software tends to run smoother.
And all that is not taking into account optimisation to Linux system themselves; there’s been a lot of improvement in technical stuff for graphic drivers (especially on AMD side, but not exclusively), the kernel itself can get improvement in its handling of IO and memory, the whole thing is more flexible, etc.
Nah. I mean, there might be some stuff like that, but nowadays, I’d be surprised if feature parity wasn’t 1:1 (or even better, with some open source drivers having features that are removed from official windows drivers…).
The underlying OS is pure garbage, that’s mostly it. Windows will start chugging everywhere with even moderate FS activity: running a background, single-threaded backup process will sometimes make it impossible to click in another window or open a new application. Driver API is not great, you have to jump through hoops to do basic stuff. There are many ways to do the exact same thing, each being more or less efficient than the other. Audio API is so bad, an audio device failing will sometime cause ohter, unrelated, non-audio application to spontaneously combust.
And so on and so on.
On the other hand, the Linux compatibility layer that proton provides do add some overhead in places, but surprisingly, it’s not that much overhead. And it’s not that common (basically, the code runs natively until specific instructions that requires special handling).
Obviously, when you have a better operating base, and very little extra overhead, software tends to run smoother.
And all that is not taking into account optimisation to Linux system themselves; there’s been a lot of improvement in technical stuff for graphic drivers (especially on AMD side, but not exclusively), the kernel itself can get improvement in its handling of IO and memory, the whole thing is more flexible, etc.