SeLinux can be a minor nuisance if you have a container centric workflow. Otoh podman is a first class citizen.

Other than that it's pretty good. I've had some pain updating so I went back to Arch / void. All my servers are Fedora and I much prefer it over Debian as it's somewhat up to date.

See also duckdb and clickhouse for OLAP of course.

I am a little bit out of the loop as the news can be a little bit depressing for daily intake.

I know she was shot. Was that her home? Was she just watching the protest / shitshow or was she involved in the protest in some way?

Obviously, people shouldn't be shot for being involved in a protest, and it doesn't really colour my opinion on it one way or the other, but I think if that's where she lived there this should be an open and shut case of murder.

Many games just work. The ones that don't, don't bother and your g2g.

If you really want the games that don't work just dual boot or playstation.

Memory safe languages that are not garbage collected are not all that common. Ada and Rust are two examples.

With great care C++ and zig can be.

I'm sure there's a good reason a lot of the big players and the community at large have picked up rust though. Docs, error messages, cargo community etc.

I would argue that Rust does bring a lot to the table. I certainly would never code in C for work but I'll happily reach for Rust.

Similarly, translating from html/QML or js/py/rust is handy.

Its still a pain because even good models like opus are hit or miss. The code still has to be reviewed and adapted. Can save time though.

They are also very useful for mocking up a quick proof of concept.

Is X doable? Will Y potentially solve the problems that my clients need me to solve? mock it up in two seconds with a few prompts and a language model and you don't have to take a stroll down a garden path.

The actual work I still have to do but that's why I'm paid to do it.

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 agree.

It may undermine a person's self-image without indicating they think any differently about other people's sexual interests or perhaps even their own.