[flagged]

All the stuff trying to implement a protocol are usually better off using a language that has sum types imo, and I think that's a big enough argument to dismiss C.

Considering that LLMs more often than not forget stuff when writing code, I definitely prefer Rust's automatic memory management system compared to balancing mallocs and frees throughout the code.

You could do RAII in C++, but the compiler won't warn on unsafe code.

Basically any deterministic process that can look at your code and guarantee a certain useful property is worth it's weight in gold with AI driven software development processes because it significantly reduces the review burden.

Meanwhile the C ecosystem is currently collapsing from AI finding critical RCE vulnerabilities in infrastructure projects written in C.

Hyperbola GNU and C99 half-lover there. C it's fast, but for networking clients/servers Rust it's far more secure, even more with current AI vulns. Under amd64 it should be almost mandatory. Half of Gnome would be far better with gtk4-rs. For legacy i386 users, it's either Go (aerc for email rocks) or Algol68.

C is a loaded gun pointed at your foot regarding memory management. Rust directs your gun somewhere safer. That is why.