but i still love rust ofc
https://blog.rust-lang.org/inside-rust/2026/08/18/reducing-t...
When I mentioned, after C++26 failed its vote, that maybe they should use this extra time to focus more on memory safety, I got downvoted instead.
Surely attitude isn't helping their situation.
I didn't downvote you but I didn't find your comment particularly relevant or on topic. This disapproval thing and working on memory safety don't seem related at all. Someone had the impression that you were pushing for Rust without mentioning it. Your comment might have felt like you were backseat driving as well. More memory safety in C++ would be cool, but do you have actual ideas on how to achieve this?
There are a lot of reasons people could have downvoted you. You shouldn't worry too much about it though, just relax and forget about it.
With rust, those class of errors are very difficult to arrive at, unless you specifically make it so.
with rust, the "risk" gets moved from runtime to compiletime. I'll take a 1TB build bloat over code crashing in prod. any day.
- Making sure you compile with as few profiles as possible.
- Disabling debug info (or setting it to "line-table-only") for the default profile.
I just think agents benefit a lot from having unavoidable feedback in the dev loop, and Rust affords that through its strictness. It's easier for agents to fall into the pit of success with Rust. I do think it's somewhat lacking in compile-time features, though.