I don't particularly care if it's going to happen via Rust, Fil-C or something else I care that we've reached a place where it's not plausible anymore to say that memory safety doesn't matter and that pretty much everyone accepts that better tools will be needed to achieve it

Nov 6, 2025 · 10:07 PM UTC

2
8
Replying to @the_octobro
I understand Fil-C for legacy stuff that will take forever to port/rewrite to rust but for new software where performance matters you are literally insane to not use rust. Like we might have to turn you into biofuel if you do not use rust not because it's a cult but because it's so vehemently retarded to deliberately write something _new_ in C.
1
1
I deeply agree, but if people are going to (retardedly) insist on using C, they might as well be introducing minimum basic safety features
1
Replying to @the_octobro
managed environments are memory safe, that isn’t really the issue, just look at the cataclysm of CVEs that plague Java to realize that software security isn’t just memory safety. Rust devs like to blame memory safety, but that is really just the tip of the iceberg.
1
1
And yet about 70% of CVEs would be impossible without memory unsafety.
1
more replies
Load more