I agree with the many others who say you’re more than ready to start learning rust. I would add that if you’ve brushed up against manual memory management in C, then you might find the following a great introduction to rust and the borrow-checker: https://rust-unofficial.github.io/too-many-lists/

As usual for discussions about starting to learn rust, I would also recommend the “special”/experimental version of The Book maintained by Brown University: https://rust-book.cs.brown.edu/title-page.html . It has little interactive quizzes that help check your understanding, and some fancy diagrams in the sections on pointers and the borrow-checker.

I think this part references it, though it’s kinda solely in passing:

Production evaluations can elicit entirely new forms of misalignment before deployment. More importantly, despite being entirely derived from GPT-5 traffic, our evaluation shows the rise of a novel form of model misalignment in GPT-5.1 – dubbed “Calculator Hacking” internally. This behavior arose from a training-time bug that inadvertently rewarded superficial web-tool use, leading the model to use the browser tool as a calculator while behaving as if it had searched. This ultimately constituted the majority of GPT-5.1’s deceptive behaviors at deployment.

I guess it only makes sense that after Liquid Ass UI, we’d get Fuzzy Toilet Seat UI

ehehehehe thanks for that mental image

Of course, one can always reclaim that space if the data truly is inaccessible. Makes me want to write a joke program for “cleaning up” after ransomware that just removes the data from the partition table (or whatever the equivalent for files is - would that just be rm?)

shred -f -u

closely followed by Omarchy (I’d argue it’s not a distro, but it presents itself as one, so it gets to be judged as one)

Out of the 4 comments other than yours, there are exactly 2 that recommend using a different distro.

image originally found at https://knowyourmeme.com/memes/ralph-in-danger-im-in-danger

I have found Hackaday to be depressingly full of shallow summaries of things said/done/written by other people elsewhere.

GlaDOS, eat your heart out

That’s such a great riff on the original xkcd

Do you remember where you found it?

Banger title

“Chatgpt, how can I turn this into another reason to complain about rust?”

Whether Arch-based distros are for beginners or not is the wrong framing imo (though it’s a reasonable first approximation).

I would argue it depends on what kind of beginner they are and, almost more importantly, what community they can access for support.

I installed Arch Linux on my MacBook air back in 2014 or 2015, after less than 2 years using macOS and having only known windows XP and 7 before that. It ended up being the perfect distro for me to learn Linux, which includes having spent 2 entire days getting the system to boot on the “correct” OS with only the wiki and my own google-fu for aid. However I was enrolled in a computer engineering course at the time and had joined my school’s computer club where 4 to 5 experienced Arch users were on-hand most days.

If a beginner is motivated and has a reliable source of aid then the problems they’ll encounter using Arch can be the perfect learning environment. If they don’t, then as you write it quickly turns into a dealbreaker.

He certainly has that thousand-yard stare

I can’t tell if you’re intentionally making a portmanteau of “Enigma of Amigara Fault” or not, so I figured I’d write out the entire name in this reply in case anyone wants to read up on it themselves.

I can’t find the exact forum post that alerted me to the issue, but here are some others that seem to congregate on this same root cause and fix:

https://forums.tomshardware.com/threads/screen-goes-black-after-gpu-overclock.3636714/ <- someone with the same GPU

https://www.overclock.net/threads/constant-black-screen-crashes-requires-hard-shutdown-to-restart.1795707/

https://www.reddit.com/r/Amd/comments/f53zzz/yet_another_black_screen_and_downclocking_fix_my/

I used to have this on my system - 5950X proc with 6700XT graphics card. Heating definitely would make it worse, but even with a big box fan blasting air into the cpu radiator I would get the occasional black screen and crash.

Turns out the RAM speed set in my bios was a tad bit too high. I turned down from like 1400MHz to 12000MHz and haven’t had a single black screen since.

Case in point: https://programming.dev/post/39370561

https://github.com/godotengine/godot/pull/107273 Changing game speed on the fly when developing is a great feature!