That's not my point, I don't contest that safe languages are safer. I contest the idea that we should "just use" something else. All my tools are written in C, the entire GNU toolchain is in C, how am I supposed to operate in this world if I "just don't use" C?

That is the disadvantage of open-source, it forces you to use the language of someone else's source.

I used Delphi on Windows. Most of the code I wrote in the last 20 years is in Pascal.

And that works really well on Windows. You have a stable API, and it does not matter what language the API is written in. Any language can use the API in the same way.

I tried to run some old projects this month. My 20 year old Delphi Windows programs run better in WINE on Linux than most programs I wrote 5 years using Linux tools, because the libraries have changed, but the API has not

I think OP was implying not to write new code in C. If possible, we can also use replacement tools written in safer languages if they offer the functionality we need (e.g. `ripgrep` instead of `grep`, or web servers written in safe languages over those written in C/C++).

ripgrep isn't POSIX compliant. It's hardly a proper replacement.

Right, it is intentionally not POSIX compliant. This saves fairly significant development effort and also permits expanding the tool to be more user friendly, such as transparently searching UTF-16 encoded files.

ripgrep cannot be a drop-in replacement. Despite that, it can certainly replace grep in a wide variety of use cases. See: https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#pos...

Congratulations. You have succesfully regurgitated the same sentence I've read here a thousand times.