• 0 Posts
  • 79 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2023

help-circle

  • pre-ryzen AMD CPUs were always a bit on the budget side even when they were new. They were a bit more power efficient and cheaper, but never were amazing performance. So yeah, a 15 year old CPU is often rough, but a 15 year old low-mid end CPU is going to be even worse off.

    Ive not had issues with Counterstrike 2 on linux, aside from wanting to play FaceIt or ranked matches that have stricter third party anticheat. And that’s just the anticheat being the problem.

    I would venture a guess that linux is not “the problem” here and it’s more likely just aging hardware meeting increasing game demands.

    The only time in recent years I’ve had specifically a problem with linux gaming performance (not related to anticheat), was playing VR on a pre-GCN AMD GPU which didn’t support async reprojection properly which caused quite a bit of stuttering.




  • Steam deck highlights that Windows -> SteamOS translation is good enough.

    I’ve use my Index on Bazzite successfully with no issues, so I’m confident in SteamOS VR capabilities.

    ARM-based is the only wildcard, but if fex works, then that’s not an issue either.

    Then just onboard compute performance is the only factor. But like you said, even if this winds up only being a “stream everything, its a wireless index,” then I’m already excited.




  • You don’t have to have been a slave to have dealt with racism. Enough people still get really excited about their confederate flags that clearly the era is still heavily topical.

    The word “confederate” means nothing beyond referring to a type of government, but when I hear it, I think immediately of the American civil war. Even though that ended in 1865 so I was never alive to witness that.

    That’s not how word associations work.


  • Yeah. theres a fine line between advocating for positive change because it’s the right thing to do vs because it makes you look good. Theres a fine line between being an ally and empty virtue signalling, and those things may not look different within the scope of a single interaction. It can sometimes take a bit to understand if someone is genuine or just performing.


  • bisby@lemmy.worldtoProgrammer Humor@programming.devmaster vs main
    link
    fedilink
    arrow-up
    52
    arrow-down
    3
    ·
    2 months ago

    The point of political correctness is that it’s always things you’d never consider… but someone else does. I’m not here to say whether things are right or wrong or if “master” is good or bad. but you perfectly highlight the reasoning behind it.

    To you, the only thing that comes up is the technology context. And that’s perfectly reasonable. To someone else, the unrelated slave owning context may just be tightly coupled with that word, and that immediately comes to mind when they hear the word regardless of context. And someone in that scenario is probably not having a positive correlation with the word.

    So a group of people have a very understandable reason to have a negative correlation with the word, and it’s super easy to use a different word, so it seems to make sense to just use the other word.

    All my git scripts these days have a $(git remote show origin | sed -n '/HEAD branch/s/.*: //p') in them, which just fetches whatever origin calls the head branch. so if I want to rebase from main/master/prod/lead/front/etc … the command will figure out which one to use for me.



  • Not detecting case fans sounds like it would be not communicating with the motherboard properly. Unfortunately every specific motherboard is going to have it’s own unique set of constraints. But generally this is all handled through “it87” i believe? But it87 can sometimes take some nonstandard params.

    Here’s an example gist of instructions for getting things working on one specific motherboard. https://gist.github.com/bakman2/e801f342aaa7cade62d7bd54fd3eabd8

    The wifi7 on my motherboard causes kernel panics pretty regularly, and the RGB isn’t properly exposed so I cant control(/turn off) any of the lights. Usually these things work themselves out with time as drivers for the new/nonstandard chips make their way into the kernel/libraries.


  • Yeah. In college world, one needs to be prepared for the school to not care at all and declare that it is the student’s responsibility to make sure any required software runs on their machine. And college can be a hectic stressful time, so finding time to be able to get things working on Linux may not be worth it. Having the Windows escape hatch ready is very important to be able to not lose your mind while on a deadline.


  • I’m not raging and I’m not even saying that Debian is bad. I’ve just been told MANY times over the years (including on Lemmy), when I’ve commented about bugs and issues I’ve had on Debian, that stability doesn’t mean “without bugs, always upright” it means “not moving, not changing.”

    Debian has a very specific use case. And when people say Debian is stable they mean the base platform isn’t going to change under you and suddenly a config file doesn’t work anymore because Package v2.0 uses a different format.

    This is good for people who want a low maintenance system that won’t unexpectedly break due to a random Windows update.

    This is good for probably the vast majority of people that fall under “normal” computing habits. If there was a major groundbreaking bug that affected everyone, it probably would have been caught in testing.

    This is not good for people who have quirky computing needs or otherwise do things in slightly niche ways, IF a bug shows up. Some bugs are minor annoyances, some require different workflows to get around.

    But ultimately, people should know that if they are experiencing an issue with Debian, and it’s not just a configuration issue, they either need to have a solution for themselves (recompiling), or switch distros.

    I personally stopped using Debian for my desktop around linux 3.16 days, but I do still use it for my home servers (where I don’t want to be updating things constantly). If Debian works as a desktop platform for you, that’s awesome.

    But OP was having issues with Debian. So OP should know that due to Debian’s unchanging nature, it will be quite a while before things start working. And they shouldn’t expect otherwise. And that’s ok, their use case is going to just be a bit more bleeding edge.


  • Ok? “You only have to wait a few months for this crash to be resolved.” still doesn’t resolve people’s issues.

    “Fix playing of custom alarm sounds” doesn’t sound like a severe issue to you, but it was also something that if someone needed, they were forced to wait a few months.

    Debian would rather have broken custom alarm sounds for several months, even if it was fixed earlier. Fixing a bug to me lands closer to a security issue than “shipping bleeding edge feature sets”.

    It ultimately means if something you need is broken for a non-security reason, it is not being fixed until the next point release. There is a fixed unit of time in which you know your problem will not be resolved.

    Packages are individually updated for security fixes. Individual packages are NOT updated for bugfixes.


  • I’ve been told plenty of times that when I had bugs that weren’t getting fixed that “stability means no unexpected changes, not uptime, compile the package yourself if you need it fixed.”

    There are plenty of examples of upstream projects asking debian to not package their stuff because they get bug reports for things that were fixed months ago.

    Debian does not ship bugfixes. Debian only ships security fixes.

    If something works, it’s not going to break. But if something doesn’t work, it’s not going to unless you fix it yourself by going outside of the official packages.


  • Also worth noting that Debian’s definition of “stability” doesn’t mean “doesn’t crash” even in the slightest. It means “doesn’t change.” That means not changing broken software to be newer working software.

    Any non-security bug that exists will stay because new software only ships for backported security updates. So if you have a crashing issue, Debian has no interest in fixing it until the next release. Unchanging is more important than working.

    If you don’t have any crashes or bugs popping up, Debian is great, because it won’t introduce crashes or bugs. Nothing unexpected will happen.

    By Debian’s definition, the Titanic is now VERY stable, unmoving at the bottom of the ocean.