It's definitely possible in C to code in a way that makes memory overflow errors impossible. It's just that it often gets overlooked, probably due to project timelines or carelessness. The benefit to Rust is that it makes the entire situation impossible, vs. C where it's definitely possible to have coded well enough that memory overflows wouldn't happen but are you totally sure you coded well enough? I'm sure C is faster than Rust (though I'm not sure how much faster) and Rust does absolutely nothing to prevent a myriad other possible coding errors, so it's not like Rust is the end all be all.
As far as what attracted troons to Rust, I'm quite sure I have no idea. Never cared enough to research it, and I only tried learning the basics of the language when it became the new hot topic on all the software developer applications.
As far as what attracted troons to Rust, I'm quite sure I have no idea.
Primarily because Rust was developed at Mozilla after it was infested by troons. So they latched on to it early because it was their baby (even though it was actual talented non-troon computer scientists that made it).
But also because they gravitate to rules and authoritarian systems so the more rules and the less choices in the language the better for them. They're generally not very intelligent so they want the guardrails to not make stupid choices. Paint by numbers.
Another one like this is Google's Go language. Rob Pike was at least troon-adjacent himself, but it attracted more than a normal share of weirdos because it dictated source formatting and file organization and a bunch of other arbitrary decisions for no good reason. They love arbitrary rules.
It's definitely possible in C to code in a way that makes memory overflow errors impossible. It's just that it often gets overlooked, probably due to project timelines or carelessness. The benefit to Rust is that it makes the entire situation impossible, vs. C where it's definitely possible to have coded well enough that memory overflows wouldn't happen but are you totally sure you coded well enough? I'm sure C is faster than Rust (though I'm not sure how much faster) and Rust does absolutely nothing to prevent a myriad other possible coding errors, so it's not like Rust is the end all be all.
As far as what attracted troons to Rust, I'm quite sure I have no idea. Never cared enough to research it, and I only tried learning the basics of the language when it became the new hot topic on all the software developer applications.
Primarily because Rust was developed at Mozilla after it was infested by troons. So they latched on to it early because it was their baby (even though it was actual talented non-troon computer scientists that made it).
But also because they gravitate to rules and authoritarian systems so the more rules and the less choices in the language the better for them. They're generally not very intelligent so they want the guardrails to not make stupid choices. Paint by numbers.
Another one like this is Google's Go language. Rob Pike was at least troon-adjacent himself, but it attracted more than a normal share of weirdos because it dictated source formatting and file organization and a bunch of other arbitrary decisions for no good reason. They love arbitrary rules.
What makes you say that? I only know a little about him.