>>107527035
What is the chinese Ministry of State Security's opinion on rust?

File: hmm.jpg (6 KB, 225x224)

6 KB JPG

>>107527035
>puts its trust in
What are C#, Go, Java, and Ruby written in, again?

File: 1760196378661619.png (305 KB, 1031x1085)

305 KB PNG

was memory unsafety so bad that we need to rewrite literally everything? i don't remember ever hearing about memory issues all that much, they're treating this like it's the bug of the millennium.

>>107527035
Should have switched to Hare instead https://www.youtube.com/watch?v=6wQ7pl7DVHw

>>107527253
>was memory unsafety so bad
if you check here https://app.opencve.io/cve/?vendor=tor
they are as incompetent as it gets.

>>107527253
this just means someone was paid to do it otherwise why would you

Rust is proof that it's not a language problem, see: cloudflare incident.

Rust developers aught to take care to make their software bootstrappable and not require long chains of version upgrade compilations.

>>107528187
According to rust devs, doing so with gcc-rs is a very bad idea.

>>107527035
Is it a bad time to start learning C++

File: 1762528273895060.png (112 KB, 2400x2000)

112 KB PNG

>>107527253
Memory safety is just so good that you need to rewrite everything,

>>107528449
It's funny how sane people think that improvements should be done in small parts, on most important, and more importantly, newest code only.
Rustroons write no new code and their npm clone only enforces that.

File: pepe33.png (236 KB, 528x438)

236 KB PNG

>>107527035
Why is the TOR project constantly making very sus decisions lately?
This is just one of many in the recent years.

>>107528514
You need complete memory safety to get the win of memory safety: Eliminating process context switching costs.

>>107528681
Last I checked, rustroons rave about async and async is all about generating as many context switches as possible.

>>107527253
Memory safety vulnerabilities tend to be worse than other kinds of vulnerabilities because you can escalate them into e.g. arbitrary code execution, while logic bugs tend to be more situational and less interchangeable.
They're a big deal in browsers and such. Those systems apply lots of different mitigations to prevent memory safety issues and limit the damage they can do but it's not enough.

>>107528857
Isn't the point of async to reduce the cost of the context switches you have to make anyway? You won't do better with threads.

>>107529427
All rust async runtimes already use threads, simply put, it's misdesigned pile of crap.

>>107527035
Oh no, it's sad news.

File: 1765396358959230.png (608 KB, 1893x806)

608 KB PNG

>>107527035
Good
Now spread this so that a new forks will reborn

Rust has a backdoor, same as Java. C compilers can have them too but C is simple enough that there are from-scratch compilers written in assembly and so on.

Rust, Java, these "safe" troon languages all emanate from one big globohomo company or organization. There is only one implementation which is usable and the language will be arbitrarily updated over time to enforce this, making it impossible for anybody to catch up to Rust from five years or ten years ago let alone Rust as it is today or tomorrow.

>inb4 point to the backdoor
Go look at the CVE list for Rust and its cargo crates. New ones are inserted regularly as the older ones are discovered, as with Java and .NET.

>>107527253
Memory unsafety wasn't as bad in the past but as C and C++ became more popular and replaced safer languages like BASIC, FORTRAN, COBOL, ALGOL, PL/I, Pascal, and Ada, there are more and more memory bugs. Even Lisp, APL, ML, and Prolog used to be more popular than C.

>>107531022
>C compilers can have them too but C is simple enough that there are from-scratch compilers written in assembly and so on.
You're confusing C with Pascal, Oberon, or FORTRAN. C is such a complicated language that most C compilers are written in C++ because writing a C compiler in C is too hard. Nobody even knows what a line of C does because the standard is so ambiguous.

>>107531096
And yet, it's a common fun practice for people to write their own little C compilers in assembly.

Nobody writes compilers for Oberon except that one guy who decided BASIC must be taken away from the common man, he's a very stupid haughty faggot.

>>107531115
>And yet, it's a common fun practice for people to write their own little C compilers in assembly.
Not at all. TCC is written in C and it's only a toy compiler. The rest are written in C++.

>Nobody writes compilers for Oberon except that one guy who decided BASIC must be taken away from the common man, he's a very stupid haughty faggot.
I didn't realize Linus Torvalds wrote an Oberon compiler. Maybe I should have more respect for him.

>>107527035
How does this solve the problem of 99.6% of all Tor nodes being run by the US Government?

>>107527153
none of those are memory safe, they don't protect against race conditions

>>107531482
Niggga, learn to write multithreaded code.

>>107531482
>they don't protect against race conditions
Are you accessing shared memory without fences and mutexes?

I'm sorry to tell you this but no matter how good your compiler is it can't make you not a retard.

>>107531060
>Memory unsafety wasn't as bad in the past but as C and C++ became more popular and replaced safer languages like BASIC, FORTRAN,
Most apps were written in Assembly, *maybe* pascal later on (when basic was popular many pascal runtimes were so fucking huge they need dual floppy drives and would swap while the app was running.)

So this means only child rapists can audit the code.

It's over.

>>107532033
Yes, but those other languages were still more popular than C and C++. Assembly isn't a high-level language.

File: Screenshot from 2025-12-1(...).png (129 KB, 864x685)

129 KB PNG

>>107527035
>hey i heard you like pozz
>so i put pozz in your pozz
cargo is like sharing needles you found under a park bench
but yeah, sure, go ahead
better fail often
bc better fail early