>>107201134 (OP)
>20% of their codebase still has known memory safety vulns
>they expect ffmpeg to fix all the vulns they report instantly

>>107201134 (OP)
oh, this is why they can't support side loading anymore

File: 1739626570067148.jpg (158 KB, 768x1024)

158 KB JPG

>>107201134 (OP)
total rust domination
and we're just getting started

>>107201199 (checked)
i'm gonna side load this foot right up your ass

File: drew segfault.jpg (353 KB, 1317x1188)

353 KB JPG

>>107201134 (OP)

>>107201134 (OP)
>legacy coder
>right side of history.

File: file.png (1.02 MB, 1585x793)

1.02 MB PNG

>>107201134 (OP)
>>107201231
>rust tranny got banned for spamming and using "sage"
>well.. i guess i should post this trash again
>1000x reduction
>according to the rust project's major backer
embarrassing

>>107201134 (OP)
What does this graph even mean? 80% of code written in 2019 was "unsafe"? What?

>>107201134 (OP)
>1000x reduction in memory safety vulnerability density
nigger what the fuck are you shipping
you shouldn't have 1000 memory safety INCIDENTS
you don't need rust, you need jesus

>>107203020
presumably they mean code written in a way which is not guaranteed by the language/compiler to be memory safe. obviously any code in any language /can/ be memory safe, but rust and the like are specifically designed to provide methods of writing code that is actually guaranteed to be memory safe. at least, that's how i understand it

>>107204194
Ah I guess. Ridiculous.

>>107201134 (OP)
Rust GODS won.
>same level of unsafety bugs for new unsafe code
how are people coping after Google btfo literally every cnile cuck post, especially the deranged "UM RUST UNSAFE {} IS LESS SAFE THAN C" cope?

>>107201292
>Caring about irrelevant platforms
>gcc mips is a buggy mess that's worse than Tier 2 support Rust targets
this posting is so fucking stupid and disingenuous. most the platforms "GCC supports" that LLVM based languages don't are all broken dogshit as well. at least LLVM and Rust are honest about this. I'm surprised they even merged m68k target in llvm.

>>107204696
don't worry. /g/eets can COPE and do cognitive dissonance effortlessly.

COPE example
>lol rust is not a memory safe language. there is no such a thing anyway
>lol so the number of bugs in rust projects is >0. i thought all rust programs are 100% correct. curious?
cognitive dissonance example
>lol rust has no jobs
>lol <every big company> is incompetent/pozzed/(((them)))

>>107201134 (OP)
>C and C++ in the same category
Completely different things. Is this rust propaganda?

>>107201153
>they expect ffmpeg to fix all the vulns they report instantly
Nope, just within the standard 90 days. Alternatively, ffmpeg could have a quarantine phase for new patches and let google et al. fuzz them first. Or, if they want to merge things right away they should also be willing to revoke the offending commit and ask the original submitter to re-submit when it's memory safe. Plenty options that don't involve whining on xitter.

File: 71894921_p10.jpg (519 KB, 1100x1000)

519 KB JPG

>>107201626
>moderate vulns

>>107205468
True, C is much worse since you don't even have basic data structures or algorithms or a standard library that isn't brain damaged beyond belief.

>>107201134 (OP)
> "right side of history"
> It's literally just a programming language like every other
Do you think you're on the right side of history for forcing half-baked CVE-infested Rust reimplementations on popular GNU/Linux distros?
Glowies never stopped glowing I guess.