@federico3 likewise with commit frequency/recency. Programs are not produce—we shouldn't assign high value to "freshness".
"ugh, repo is inactive" reactions presume that correctness is not and cannot be a thing and that a project can never (shouldn't?) even approach a state of being "finished".
People seem to use activity as an inexpensive but flawed way to approximate developer responsiveness. If that's what you care about, though, then focus on that instead of inaccurate proxy measures.
"If The World Was Created By A Programmer"
The last panel had me in tears 😂
This stuff never ceases to amaze me - Haruki Nakamara's mechanical paper animals: https://geecr.com/product/nakamura-paper-toys
Though ITX 3600 + 3060 did sound like a cool idea...
German language is magical: https://youtu.be/gG62zay3kck (feat. Rhabarberbarbara)
https://youtu.be/eZFWDh8ZjFw don't judge me, I love it 😄
Apparently the `--stress` parameter to https://github.com/ComputationalRadiationPhysics/cuda_memtest is what I was missing to diagnose the failing GPU, it identified a memory issue pretty quickly. Now to figure out if there is a Linux BadRAM alternative for GPUs...
Soooo, I've knowingly bought a cheap second-hand 1080Ti that's a bit "broken" - visual artefacts pop up on the screen occasionally, and I managed to lock up the system too (Doom on 1440p ultra - ran smoothly until it didn't). I ran cuda_memcheck and it showed no issues. Are there any GPU diagnostic tools that could identify what's wrong?