• 5 Posts
  • 86 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle


  • This is fine. I don’t mind a diversity of opinion here. I agree that Proton is a stop-gap solution, and that most older games are going to need it, and newer AAA games are not going to support Linux all of a sudden.

    However, I do think that we should continue to encourage developers to create native builds when they can. Indie devs tend to do this and it’s a pretty great experience. Not only that, it often enables playing on unusual devices such as SBCs. For example, UFO 50 was made in Gamemaker, which offers native Linux builds, and it’s already on Portmaster. You basically can’t do that with Proton.

    My problem is calling people who want Linux native games misguided or wrong. I really don’t think that’s helpful.


  • I wish he wouldn’t repeat the idea that Proton is acceptable to game devs and Linux users shouldn’t demand native games. I’m much closer to Nick’s (from Linux Experiment) idea: That these games work as long as a company like Valve pays for Proton. The day Valve stops is the day these Proton games start to rot. For archival, for our own history, and for actual games on Linux, we should want Linux native games.

    The thing is, the “no tux no bucks” crowd doesn’t advocate for other people to say the same. The proton crowd is actively telling the “no tux no bucks” people to shut up, and it’s not very nice. We need a multitude of views to succeed in the long term as a community.















  • I’m just using it as a space heater for my study, which is also where I work from. While using the computer in Winter I just switch on f@h for both CPU and GPU (AMD 5700x and 6700xt), and this heats up the room. It’s a good 300-400W. I have home assistant telling me the temperature in the room and it bugs me to turn it off if it’s too hot. That’s my “temperature control”. I didn’t build anything, the computer is just under my desk and it heats up my room.

    Originally my plan was to have F@H automatically turn on and off based on temperature, but it turns out the power is low enough and the lag is high enough that you switch it on in the morning, and then once the room is upto temperature you can just switch it off and the room will stay warm the rest of the day.


  • I do this. If you want to actually want to use or donate the processing power, this is kind of a good thing. However, there are a lot of downsides:

    • Computers are generally much lower power than a heater. This makes them very slow to “react” to heating needs. Heating a small room, even with a 500W PC, could take an hour or maybe more.
    • Heaters have a thermostat, which computers don’t, so even though they are very laggy, they also don’t stop heating when the temperature is right. This means they can overshoot and make the room uncomfortably hot.
    • You could set up an external thermostat but then you need a load which can be switched on and off.
    • I was using folding@home, but the work items take a long time, and switching them on and off will increase the time taken to resolve the work item, which in turn means the system could get annoyed and use someone else’s computer to resolve the work item faster, or worse, blacklist your computer.
    • Using your PC to generate heat will use up its maximum lifetime. The fans aren’t built to be running at max speed all the time, the CPU & GPU could wear out, and the power systems will also wear as time goes on. You sort of have to align that lifetime against usage. This is likely fine if you see the computation as a donation or if you have important stuff to compute, but it’s probably not worth just wasting the cycles.