Rust adds another layer of trusting the compiler isn’t backdoored. All UNIX/Linux systems use the gcc toolchain, so having it written in C would mean less dependencies for the OS.
You know that bans/removals are documented right? If you don’t see your post it’s because you didn’t post it. You’re not being censored, go take your meds
Weak gaslighting attempt but if you could show me where to find it documented I would appreciate that.
If anyone is confused, feel free to ask me for proof I’m telling the truth. If I posted it here, I’m pretty sure I’d be at risk of getting banned for evading the post removal (because the proof would also lead you back to the reply chain that was removed)
Edit - maybe this counts as proof without showing any removed content:
More like Rust has rotted someone’s brain. “Hey, I can’t code safely, so I will use this new toy that is supposed to make me”. This line of thought is OK as long as it does not get imposed on anything I do as a programmer
The industry cannot code safely. There are many reports, studies, and corporate disclosures highlighting that memory related bugs are the primary source of critical security issues in C and C++ code. That is why even NIH companies like Google and Microsoft are adopting Rust in their core products.
That you want to publicly ignore all that evidence to paint it as an individual skill issue does not come across as competent or intelligent. Few of us are going to assume your code is free of these kinds of bugs.
The fact that your have to say it so dismissively makes me think that you know it too.
Want a bug free code - do bug free code. Spend time carefully evaluating every line and interaction
Want third-party code and safety - examine that code in the same way
Whatever you do, assume there is a bug in any software you use, so plan and organize accordingly
No amount of magic pills can substitute the above. So yeah, it is a skill issue. Also an issue of kids wining that there are bugs and they don’t feel safe, so they want to cling to magic pills instead of dealing with the reality
It’s not a “magic pill”, it’s another tool. We’re not saying that it will magically fix everything, it will just make certain types of errors less probable.
If you want bug-free code, will you (A) use a tool that makes it easier, or (B) use the same tool as before?
I am not the person who said “C++ has rotted their brain”. I have not expressed a similar sentiment. I have never said that “borrow checker fixes all”, in fact I said that it will not magically fix everything.
And if I want a bug-free code, I will use same tool as ever: my brain
Is your brain infallible?
The strategy is not to 100% eliminate every bug in existence or theory, bugs are inevitable. The strategy is Swiss cheese security.
Something is better than nothing. Therefore (brain + something) > (brain + nothing). As long as “something” works to prevent bugs, to any extent, it will result in fewer bugs.
Strange times.
how many compiler back doors have we seen versus use-after-free/stack overflow attacks?
The anti-Rust crowd baffles me. Maybe C++ has rotted their brain to the point they can’t “get” the borrow checker.
My only complaint is that its syntax is an ugly mishmash. Should have copied scala or f#
Strange how your bad faith reply is still here, and with many upvotes, while my reply calling you out appears to be gone.
This is an example of how discussions like this are more appropriate for nostr, where there are no bans / post removals.
You know that bans/removals are documented right? If you don’t see your post it’s because you didn’t post it. You’re not being censored, go take your meds
Weak gaslighting attempt but if you could show me where to find it documented I would appreciate that.
If anyone is confused, feel free to ask me for proof I’m telling the truth. If I posted it here, I’m pretty sure I’d be at risk of getting banned for evading the post removal (because the proof would also lead you back to the reply chain that was removed)
Edit - maybe this counts as proof without showing any removed content:
https://piefed.social/post/1458050/comment/8784509#replies
If you click the link, it’s blank, yet it has a “parent comment” link that leads to where I was replying
Edit 2 - tried to post an archive link but archive.org didn’t seem to work the way I thought?
Is the link I posted above showing what I described for other users?
https://lemmy.zip/modlog?page=1&actionType=All&userId=25498760
Nope, not seeing it there
Yeah I know you don’t. It’s because your comments aren’t being removed
So this link shows a comment for you, not just a blank space? https://piefed.social/post/1458050/comment/8784509#replies
Here’s a screenshot of what I’m seeing
Can confirm that post still exists. I just downvoted it. Still exists when I open the link you posted in a browser, too, just collapsed.
More like Rust has rotted someone’s brain. “Hey, I can’t code safely, so I will use this new toy that is supposed to make me”. This line of thought is OK as long as it does not get imposed on anything I do as a programmer
The industry cannot code safely. There are many reports, studies, and corporate disclosures highlighting that memory related bugs are the primary source of critical security issues in C and C++ code. That is why even NIH companies like Google and Microsoft are adopting Rust in their core products.
That you want to publicly ignore all that evidence to paint it as an individual skill issue does not come across as competent or intelligent. Few of us are going to assume your code is free of these kinds of bugs.
The fact that your have to say it so dismissively makes me think that you know it too.
Things are much simpler:
Want a bug free code - do bug free code. Spend time carefully evaluating every line and interaction
Want third-party code and safety - examine that code in the same way
Whatever you do, assume there is a bug in any software you use, so plan and organize accordingly
No amount of magic pills can substitute the above. So yeah, it is a skill issue. Also an issue of kids wining that there are bugs and they don’t feel safe, so they want to cling to magic pills instead of dealing with the reality
It’s not a “magic pill”, it’s another tool. We’re not saying that it will magically fix everything, it will just make certain types of errors less probable.
If you want bug-free code, will you (A) use a tool that makes it easier, or (B) use the same tool as before?
“Skill issue” is not an answer.
Wrong reasoning, friend:
Yeah, sure. Borrow checker fixes all. This is exactly the idiot attitude I am addressing.
And if I want a bug-free code, I will use same tool as ever: my brain
I am not the person who said “C++ has rotted their brain”. I have not expressed a similar sentiment. I have never said that “borrow checker fixes all”, in fact I said that it will not magically fix everything.
Is your brain infallible?
The strategy is not to 100% eliminate every bug in existence or theory, bugs are inevitable. The strategy is Swiss cheese security.
Something is better than nothing. Therefore (brain + something) > (brain + nothing). As long as “something” works to prevent bugs, to any extent, it will result in fewer bugs.
Right. So what do you want with me?
No, but human brain is the only thing that can define bug
Any programming language does
There’s an ongoing effort to get gcc to compile Rust.[1]
https://lwn.net/Articles/907405/ ↩︎
This seems relevant:
https://youtu.be/Fu3laL5VYdM