Large language models are incredibly useful for replicating patterns.

They’re pretty hit and miss with writing code, but once I have a pattern that can’t easily be abstracted, I use it all the time and simply review the commit.

Or a quick proof of concept to ensure a higher level idea can work. They’re great for that too.

It is very annoying though when I have people submit me code that is all AI and incredibly incorrect.

Its just another tool on my belt. Its not going anywhere so the real trick is figuring out when to use it and why and when not to use it.

To be clear VC was version control. I should have been more clear.

Its like a gas can over a match. Great for starting a campfire. Excellent for starting a wildfire.

Learning the basics and developing a workflow with VC is the answer.

For clarity sake, I have not tried Manharo and have no opinion on it.

I take this a good thing I’ve heard about it though :)

Arch has been very stable for me if you update regularly. Endeavour OS also has been quite good. More so than both Ubuntu and Fedora have been IME.

I haven’t tried Manjaro but I’ve only heard bad things.

My recommendation to anyone starting out: Endeavour OS is an excellent compromise between the complexity of eg Gentoo or Void and the abstraction of eg Ubuntu. The wiki on its own is good cause enough.

Grab an old Thinkpad and Install Arch from scratch following the wiki. It’s considerably easier than e.g. Gentoo and equips you with enough experience to debug things.

Grab a note taking app like Joplin / Obsidian too.

After that try writing a pkgbuild and configuring sway/Hyprland/DWM.

Keep something simpler for daily driving so you don’t get warn out (eg EndeavourOS/Fedora/OpenSuse or something along those lines).

IME Endeavour is a nice compromise between over engineered bespoke behaviour like eg Ubuntu and configuration pains like Void / Gentoo.

I have a few systems that aren’t systemD so it’s just a habit I’ve built up.

In this case though it’s good for keeping an eye on it whilst debugging.

As others have suggested, it sounds like an Out of Memory situation.

Install earlyoom and tmux then run earlyoom in a tmux session and see if that helps, it will also give you handy logs to help debug.