That’s some expensive cereal…

deleted by creator

So you’re saying that you don’t like trying to relight the thermal oxidizer for the formaldehyde stream that went out due to spillover from another process, with an emergency flare? Got it.

I mean, sure, things like that are super dangerous, but at least they’re obviously, flashily dangerous and for that reason have a lot more attention paid to them. The real nasties are arguably the ones that aren’t so flashy but are much more common amd don’t have immediate effects. Formaldehyde and benzene will give you cancer, and acrylate monomers will make it so you one day wake up allergic to the modern world.

Man I just built a new rig last November and went with nvidia specifically to run some niche scientific computing software that only targets CUDA. It took a bit of effort to get it to play nice, but it at least runs pretty well. Unfortunately, now I’m trying to update to KDE6 and play games and boy howdy are there graphics glitches. I really wish HPC academics would ditch CUDA for GPU acceleration, and maybe ifort + mkl while they’re at it.

Oh absolutely, I don’t blame KDE or arch repos lol. I did see that it was a KDE update but somehow didn’t clock the version number. I had it in my head that KDE6 was much farther off.

Didn’t realize this was happening and yay -Syu went brrr and it broke my shit. Probably doesn’t help that I’m running nvidia with linux (endeavouros). Wayland doesn’t work at all (black screen on login with only mouse ptr, wrong resolution), while Xorg is now much less smooth e.g. on the switching desktop animations. Moving windows around and in-window graphics are fine. Some graphical config stuff changed too; I’m still taking inventory.

I’m also currently playing with nvidia vs nvidia-dkms with different kernels to see if that solves anything.

EDIT: Looks like that my configuration was failing to set nvidia_drm modeset=1 correctly due to my unfamiliarity with dracut. Manually adding nvidia_drm.modeset=1 to my kernel cmdline makes Wayland work (and quite well at that), though Xorg is still laggy.

Huh TIL. Growing up with the merger, I suppose I’ve come to assume that non-merger folks have different pronunciations for any words with a- or o-adjacent spellings.

cot-caught merger be like that sometimes

Or spiced lentils… dal bhat <3

Professional zero finders of derivatives of mathematical models built from duct tape, prayers, and Jimmy’s observations from before he got cataracts.

Pure by ocular spectroscopy = it looked good enough

Pharma distillation = tossing the chemical and buying a new bottle from Sigma

Retro-retro-Cope rearrangement = no reaction happened, go home and cry

Don’t worry, I was being 100% facetious! After all, γ is generally believed to have been a hard /g/ in Ancient Greek, which is the version of Greek that “graphic” is based on and is CLEARLY the wrong way to say gif :D

Kinda sorta un-jerking (but not really) for a moment, I don’t think that I’d include the rhotic in your hypothetical pronunciation in NASA and thus would say /neæ.sə/ over /neɚ.sə/. I also don’t palatalize the U in SCUBA (/sku:.bə/, not /sk^(j)u:bə/), but I suspect that’s just a dialectical difference.

Edit: I just saw your NZ lemmy instance name and now I understand the vowel choices. Cheers!

Well, you see, the g in gif stands for “graphics” which is ultimately from Greek “γραφικός,” and because this is the 21st century, γ in front of a close front vowel is pronounced as neither /g/ nor /d͡ʒ/ but rather /ʝ/, which is pronounced a bit like English’s y, so in its purest rendition gif is really pronounced “yiff”, which doubles as homage to the online communities that OP frequents.