I agree with the other comments that say to make it an occasional thing when it makes sense - Major game releases with things to note about playing on Linux, maybe twice-a-year check-ins on Linux gaming in general, that sort of thing. Although, I think it's very important to take your time getting methodology and facts right before really committing. Discuss stuff with Linux users in forums and such so that you can iron out misconceptions and workflow issues before you run into them. Things like getting precise data from MangoHUD or other benchmarking tools, making sure your terminology when referring to Linux stuff is accurate yet concise, figure out the ideal distro to use for benchmarking, etc. As a really mundane and nitpicky example, Bazzite isn't a modified version of SteamOS - it's (to put it in a nutshell) a distro based on Fedora that replicates a lot of SteamOS's functionality and philosophy. It might not seem like that big of a difference, but it's the kind of thing that could get misinformation out there to a novice, and something that'll put a dent on the reputation of your Linux coverage for those who are already quite familiar with the topic. Generally, I think having someone really immerse themselves into being "a Linux guy" on the team would be a great way to sort that out, but I recognize how big of a time/effort commitment that would be if no one on the team is genuinely interested in daily-driving it, and it can be hard to stretch the budget and add someone to payroll, not to mention finding the right person in the first place... tl;dr there's a lot to ponder and not be hasty about. Do research! Discuss with other users if you hit ungoogleable snags!
Comments 1
Re: Should DF introduce PC Linux Benchmarks?
I agree with the other comments that say to make it an occasional thing when it makes sense - Major game releases with things to note about playing on Linux, maybe twice-a-year check-ins on Linux gaming in general, that sort of thing.
Although, I think it's very important to take your time getting methodology and facts right before really committing. Discuss stuff with Linux users in forums and such so that you can iron out misconceptions and workflow issues before you run into them. Things like getting precise data from MangoHUD or other benchmarking tools, making sure your terminology when referring to Linux stuff is accurate yet concise, figure out the ideal distro to use for benchmarking, etc.
As a really mundane and nitpicky example, Bazzite isn't a modified version of SteamOS - it's (to put it in a nutshell) a distro based on Fedora that replicates a lot of SteamOS's functionality and philosophy. It might not seem like that big of a difference, but it's the kind of thing that could get misinformation out there to a novice, and something that'll put a dent on the reputation of your Linux coverage for those who are already quite familiar with the topic. Generally, I think having someone really immerse themselves into being "a Linux guy" on the team would be a great way to sort that out, but I recognize how big of a time/effort commitment that would be if no one on the team is genuinely interested in daily-driving it, and it can be hard to stretch the budget and add someone to payroll, not to mention finding the right person in the first place...
tl;dr there's a lot to ponder and not be hasty about. Do research! Discuss with other users if you hit ungoogleable snags!