Thread 107169842

Womp womp
Even with an army of troons harassing and forking every hobby project someone publishes they still let this slip by them? Total incompetence.

just because you can't eliminate every class of bug doesn't mean you shouldn't try to eliminate some of them

>>107169889
You act like you have scientifically proved that programs written in rust are safer. You haven't you just keep repeating it like a muppet.

Rusttroons will literally just go on the internet and lie, spin any tale and tell you not to trust your own eyes.
Google and Microsoft are collapsing spectacularly, yet they have sekret data that (trust me bro) that rust is so much better for reals

>>107169892
safe rust eliminates many lifetime bugs (use-after-free, dangling pointers/references, null pointer dereferencing, usage of uninitialised variables) and concurrency bugs (no data races). RAII also helps avoid memory leaks and manual resource management

>>107169969
Rust solves a made up problem. The majority of the "cves" and "bugs" found in c programs. What rust programmers would call "memory saftey" bugs are total bullshit. Usually some internal function that would have the programmer be the attacker. In reality your statistics are bullshit and you just use them as a political weapon to get people using your shitty memelang that will be dead in a few years due to language design issues.

>>107169969
rust introduces poor programming practices by enforcing a specific design pattern instead of supplementing existing ones. it's essentially useless in any practical scenario where safety is one of many factors, not the only one, because it turns out compromising other aspects leads to inconsistent behaviour. and what's worse, memory safety problems or behaviour inconsistency problems?

You're going to see that shit cascade 1000x if Rust ever gets any real popularity to make it a proper attack vector against real targets.
Seriously, try and compile any given mildly popular rust library and you'll see what I mean. It's like a parody of javascript's ecosystem.
>pull in five libraries that pull in 10 libraries that pull in more and so on
It's to the point that the only big company i've seen use Rust, only in small tooling, still had to make a full guide on evaluating online rust code for dependencies.

You're going to see that shit cascade 1000x if Rust ever gets any real popularity to make it a proper attack vector against real targets.
Seriously, try and compile any given mildly popular rust program and you'll see what I mean. It's like a parody of javascript's ecosystem.
>pull in five libraries that pull in 10 libraries that pull in more and so on
It's to the point that the only big company i've seen use Rust, Embark Studios, still had to make a full guide on evaluating online rust code for dependencies and they weren't even using it for anything important.

was at google when they mandated rust for new infra. team lead was a troon who spent standups crying about microaggressions. compiler shit itself on our 2M LOC and they blamed "C++ brain damage". we wrapped everything in unsafe blocks and shipped it. same memory bugs, 3x compile time, but at least the commit history has preferred pronouns.
now i write PHP for a camgirl site and sleep like a baby.

>>107169842 (OP)
owner of kiwifarms loves rust btw

>>107170364
based

>>107169974
those cves are frequently a product of google and firefox poos adding stupid features and bloat on an intense release cycle. the average ancient C software with some of the worst dev practices imaginable today and absolute amateurs all around the world contributing dubious patches for even less qualified maintainers all fare much better.