Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2026 Poal.co

848

It seems that the war on C/C++ is everywhere. "Rust" is the new kid and everyone want's you to use it.

Archive: https://archive.today/PbL2k

From the post:

>The C programming language—powering everything from operating systems to aircraft control software—has long been a cornerstone of modern computing. But its flexibility comes at a cost: memory safety issues, like buffer overflows and dangling pointers, continue to plague high-assurance systems with critical vulnerabilities, and users must constantly update their systems to avoid becoming victims of attacks To tackle this systemic risk, a team of researchers from the University of Wisconsin–Madison; the University of California, Berkeley; the University of Edinburgh, and the University of Illinois Urbana-Champaign has received a $5 million award from the Defense Advanced Research Projects Agency (DARPA) under its Translating All C to Rust (TRACTOR) program. The team’s goal is to create automated tools that can safely and verifiably convert legacy C codebases into the memory-safe Rust programming language without sacrificing performance or functionality.

It seems that the war on C/C++ is everywhere. "Rust" is the new kid and everyone want's you to use it. Archive: https://archive.today/PbL2k From the post: >>The C programming language—powering everything from operating systems to aircraft control software—has long been a cornerstone of modern computing. But its flexibility comes at a cost: memory safety issues, like buffer overflows and dangling pointers, continue to plague high-assurance systems with critical vulnerabilities, and users must constantly update their systems to avoid becoming victims of attacks To tackle this systemic risk, a team of researchers from the University of Wisconsin–Madison; the University of California, Berkeley; the University of Edinburgh, and the University of Illinois Urbana-Champaign has received a $5 million award from the Defense Advanced Research Projects Agency (DARPA) under its Translating All C to Rust (TRACTOR) program. The team’s goal is to create automated tools that can safely and verifiably convert legacy C codebases into the memory-safe Rust programming language without sacrificing performance or functionality.

(post is archived)

[–] • 3 pts

I’m gonna say darpa is pushing this because rust is a security nightmare. C and c+ less so. Old, proven. And they need to be able to reverse engineer any code and cool it security issues.

I am not a programmer per say, but I’d wager that rust can be decompiled easily not like c/c+

Fuck darpa.

[–] • 4 pts

I have a feeling that a lot of this is also due to the competency gap.

Sure, you can write code, sure it works. It probably won't be memory efficient or secure though if you don't know what you are doing. Every time a language tries to smooth over the edges they end up creating massive problems for the future.

Ruby was considered the go-to for a while (I fucking hated ruby, and ruby on rails). Then the bug/exploit with the parser came out and basically everything in the world that used ruby/ror was fucked with a massive RCE and much of it no longer maintained or to be updated.

When you write your own shit in "lower level" languages you impact yourself. Not everyone in the world. Someone that knows more than me can probably tell me I am a moron or might agree with me but that is how I feel about the "fad of the year" languages.

[–] • 2 pts

Agree. I’ll take the advice of Steve Gibson. “I program in assembler, becoase it’s efficient to run, not to write, but it’s flawless when it works, zero dependencies, and after compiled, good luck unwinding” I’m paraphrasing lots of things I read he said.

But yeah. New is shit, old is boomer. Fuck off genz learn to code you bunch of soy sipping cock gobblers.

[–] • 1 pt

I have not seen any articles about people saying how good "AI number 5" is really good at converting code to ASM and making to so much faster and more memory efficient. That might be rather telling... Don't you think?

[–] • 2 pts

The team’s goal is to create automated tools that can safely and verifiably convert legacy C codebases into the memory-safe Rust programming language without sacrificing performance or functionality.

Good luck with that.

For starters, Rust memory safety is an illusion; see cve-rs (github.com).

A wiser strategy would be to start building existing C and C++ code with Fil-C (fil-c.org). It can detect unsafe programming and you don’t need to create a mess by rewriting in a new language.

[–] • 1 pt (edited )

There's nothing wrong with C or C++, maybe the people trying use it or maybe QA, but the language does what it's supposed to: generate fast code in the CPU's native instruction set. This is like blaming guns for killing people.

Maybe they need to blame assembly language or the CPU.

[–] • 1 pt

Yeah. Its basically people that don't want to have to learn how fire works but want's to make solid state rocket engines. Or some other such insanity. They just want to "trust that it works right" and is "easier".

[–] • 2 pts

Have you heard about Cleveland sueing Hyundai and Kia because niggers steal the cars? (news5cleveland.com)

[–] • 1 pt

Yep, sure have.

I think we should deport the niggers and the people suggesting they sue the car companies because "cars are too easy to steal" should be sent with them. All to the worst third world shithole we can find and hundreds of miles from a proper road or airport so they can't find their way back even if they try.