• 0 Posts
  • 9 Comments
Joined 7 months ago
cake
Cake day: April 3rd, 2024

help-circle

  • There are many OS-related diseases. Many Linux users are affected by or at least know someone who suffers from the compulsive need to mention that they’re using Arch. Then there’s compiler flag addiction, which can develop in Gentoo users. iDependency, the pathological need to purchase any product Apple releases, has financially ruined many macOS users. Windows users’ feelings towards Windows Update and the associated increase in heart rate are known to substantially increase the risk of a fatal heart attack.

    Knowing how to operate TempleOS is considered a mental disorder under the DSM-5.




  • These days ROCm support is more common than a few years ago so you’re no longer entirely dependent on CUDA for machine learning. (Although I wish fewer tools required non-CUDA users to manually install Torch in their venv because the auto-installer assumes CUDA. At least take a parameter or something if you don’t want to implement autodetection.)

    Nvidia’s Linux drivers generally are a bit behind AMD’s; e.g. driver versions before 555 tended not to play well with Wayland.

    Also, Nvidia’s drivers tend not to give any meaningful information in case of a problem. There’s typically just an error code for “the driver has crashed”, no matter what reason it crashed for.

    Personal anecdote for the last one: I had a wonky 4080 and tracing the problem to the card took months because the log (both on Linux and Windows) didn’t contain error information beyond “something bad happened” and the behavior had dozens of possible causes, ranging from “the 4080 is unstable if you use XMP on some mainboards” over “some BIOS setting might need to be changed” and “sometimes the card doesn’t like a specific CPU/PSU/RAM/mainboard” to “it’s a manufacturing defect”.

    Sure, manufacturing defects can happen to anyone; I can’t fault Nvidia for that. But the combination of useless logs and 4000-series cards having so many things they can possibly (but rarely) get hung up on made error diagnosis incredibly painful. I finally just bought a 7900 XTX instead. It’s slower but I like the driver better.




  • Useful stereotypes can help a person avoid danger.

    Unknown mushrooms don’t have to be poisonous but being careless with them can lead to a grisly death. Drivers don’t have to be unaware of me but it takes just one who is to put me in mortal danger if I’m not careful. A man following a lone woman at night where nobody else is around doesn’t have to have ill intent but she’s still better off being prepared for the case that he does.

    Does this discriminate against mushrooms, drivers, and men? Yes, but that’s the point. It’s essentially an informal safety guideline and it deliberately overreaches just like real safety guidelines. The 999 times someone doesn’t need that handrail don’t outweigh the one time they do; not in OSHA’s eyes. Because someone might die if the handrail fails that one time.

    This whole thing becomes problematic when it gets over-applied. Avoiding canned mushrooms in the supermarket won’t protect me from poisoning. Assuming that all drivers are blind and irresponsible will not improve my behavior on the road. Being afraid of all men in all situations will not make that woman’s life better.

    Like always, Paracelsus is right: The dose makes the poison. (And like with poison, some stereotypes are so toxic that any dose of then is bad for you.)