I think it could be argued that Proton actually gives Linux and Valve control over directx instead of M$. Since, the only directx features and implementation that developers targeting Linux can use is the implementation from Proton. M$ has no say over what Proton users can use.
Furthermore, it reduces the barrier to entry for developers to support fully native Linux+opengl/vulkan, breaking developers out of Microsoft’walled garden.
I understand that the Linux community was worried about wine wrappers before, but I think Valve has shown everyone how good wine wrappers can be.
I wouldn’t call it WINE Wrapper. While I agree that this is the correct usage of the term, I’ve mostly seen it used online to describe tools like winelib or eON, meaning tools that allow to target Windows APIs at compile time.
I think it could be argued that Proton actually gives Linux and Valve control over directx instead of M$. Since, the only directx features and implementation that developers targeting Linux can use is the implementation from Proton. M$ has no say over what Proton users can use.
Furthermore, it reduces the barrier to entry for developers to support fully native Linux+opengl/vulkan, breaking developers out of Microsoft’walled garden.
I understand that the Linux community was worried about wine wrappers before, but I think Valve has shown everyone how good wine wrappers can be.
I wouldn’t call it WINE Wrapper. While I agree that this is the correct usage of the term, I’ve mostly seen it used online to describe tools like winelib or eON, meaning tools that allow to target Windows APIs at compile time.