To be honest.... Yes it's that complicated. I've read that, Apparently valve had to spent massive ressource to figure out the load order of librairies and what to include for the steam runtime.

Granted, all they made is open source iirc. But it was a massive pita

[–] wax@lemmy.wtf 3 points 11 months ago

Yes, their first attempt used load order overrides and search patch patching. Now, it uses linux containers to ship an isolated environment. Think of it as more similar to docker (or LXC/LXD). That said, I haven't used it myself to so cannot comment on how difficult it is to use. Most people here are advocating for them permitting proton use without necessarily supporting it officially though. Which can easily be done by changing an option in EAC.

[–] squaresinger@feddit.de -1 points 11 months ago* (last edited 11 months ago) (1 children)

Did you read the second line of my post?

The code changes aren't the issue.

[–] wax@lemmy.wtf 0 points 10 months ago (1 children)

Did you read my comment? They ship with libraries to unify distribution across distros

[–] squaresinger@feddit.de 1 points 10 months ago* (last edited 10 months ago)

I said: Code changes are easy, all the other things in regards to supporting playing on Linux (anticheat, support requests, testing, ...) is hard.

You said: But code changes are easy because steam has libraries to unify distribution.

Do you see the problem here?

What are you going to tell me next? That code changes are easy?