Patreon Logo Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal Logo PayPal. You can also buy games using our partner links for GOG and Humble Store.
Latest Comments by const
Broforce Is Not Coming Out Today For Linux
16 Oct 2015 at 8:31 am UTC

As long as they still work on it, I'm really not upset.
Look at where we came from. Linux gamings market-share hasn't fundamentally grown in the last years, but our expectations did.

I do work as a developer of a very, very big business application in a 50+ concurrent developers environment and tend to set up my own branch for development whenever my todo-list is filled with weeks of work. It can really help to concentrate, even though it can take some hours to do a big merge afterwards. This is not completely the same, as we have dedicated people handling the target etc., but the reasoning is pretty similar. I'd advise them to concentrate on their main target for most of the builds and irregularly run bugfixing sessions for their ports. But really, that's their decision and their experience to be made.

Rocket League Officially Coming To Linux/SteamOS, Rocket League & Portal 2 Free With Steam Hardware
28 Aug 2015 at 4:22 pm UTC

Ordered a Controller a while back and had 2 Postal keys in my inventrory. Gifted to friends, they are happy :D

Developers Of Strategy Game Halfway Show Linux Sales & Support Requests
15 Aug 2015 at 10:49 am UTC Likes: 2

Overall number of support requests is really a strange statistic. They don't tell anything about the target system/audience, unless they are unique.
On the other side, the number might just tell something about the quality of the release, as some here imply. Or not.

I don't think criticising them will solve anything. It would be way more important to plan something that we as a community can do.
How about setting up a Linux-Beta-Testers Steam Group, consisting of users with unique system configurations and developing a well organised dokumentation-/bug-report workflow.
Developers could invite the members to a (?closed?) beta and get back a report on which setups prove problematic. Then it's up to them to be open about the results on release or even decide to fix some issues upfront.