GTK client for steam

[net]

It would be pretty useful if there was a slightly simpler version of the steam client, but made with GTK. This means that GNU/linux users can have the client mach their GTK theme.

Also having said client be open source would probably make developing it easier, since I'm fairly sure plenty of other people would like to help out with such a project.

This would have many performance benefits too, making the platform more accessible to people who cannot afford a nice computer.

This would also work well with their linux friendly stance they are taking with proton and SteamOS.

[cSg|mc-Hotsauce]

Security issues and exploits are the main reason why it can not be open source.

[fschaupp]

For bare minimum Steam-Expierience one could build a wrapper around steamcli, if you want to have a very lean gui client.

I'm just woundering, why one woud like to play games on machines not even capable of running steam. I mean, aren't the games usually more demanding than the client?

[net]

Tardis님이 먼저 게시:

For bare minimum Steam-Expierience one could build a wrapper around steamcli, if you want to have a very lean gui client.

I'm just woundering, why one woud like to play games on machines not even capable of running steam. I mean, aren't the games usually more demanding than the client?

I used to have real trouble with it when I was running it on a ~13 year old laptop. However I have since moved to a much better computer and had some really persistent issues with steam being unnecessarily slow. This led me to think that since steam works in a similar way to electron which too is bad for performance, it would make sense to replace it with something like GTK or QT which is much faster.

The other thing too is that the CLI version for steam doesn't have chat which is usable, but annoying, and seems* to only work with DRM free games.

*Please correct me if I'm wrong

[net]

cSg|mc-Hotsauce님이 먼저 게시:

Security issues and exploits are the main reason why it can not be open source.

:qr:

The availability of the source code has no impact on the security. Take Keepass* for example.

This rule doesn't apply with badly made software however, but steam is relatively** good at making software, so I would assume that it is fine.

*https://keepass.info/
**See steam mobile

[The Investigator]

cSg|mc-Hotsauce님이 먼저 게시:

Security issues and exploits are the main reason why it can not be open source.

:qr:

Yes because proprietary software never gets hacked and exploited

[[N]ebsun]

cSg|mc-Hotsauce님이 먼저 게시:

Security issues and exploits are the main reason why it can not be open source.

https://en.wikipedia.org/wiki/Security_through_obscurity
"System security should not depend on the secrecy of the implementation or its components."
If the security relies on people not knowing something, that's pretty bad.