Rust was among the first more well known projects, which adopted a Code of Conduct, then grifters in the OSS community cried censorship, which made people flock to it to “own the right”. Even if I think it’s an overrated marriage of flesh between C and OCaml, Code of Conducts are generally a good thing, and the people who really like toxic callouts arre more of an anomaly, and likely were flown there due to the culture war stuff.
People hate rust because of its fences/training wheels, not because it’s “woke”
…actually I just saw someone in this very comment section ranting about “soydevs”, you’re not wrong. But there are valid complaints too! Some of us are just old and think our computers should do whatever we tell them up to and including “shit yourself and catch fire”
But there are valid complaints too! Some of us are just old and think our computers should do whatever we tell them up to and including “shit yourself and catch fire”
I agree with this, but I think rust is fine here. It has unsafe as a keyword that let’s you do the breaking stuff, it just makes sure you know you’re doing something dangerous and makes it stand out for code reviewers
That’s why I prefer D’s approach for memory safety. Sure, it’s not as well featured as Rust’s, however it has “fat pointers”, three levels of safety, and kind of optional garbage collector.
Rust was among the first more well known projects, which adopted a Code of Conduct, then grifters in the OSS community cried censorship, which made people flock to it to “own the right”. Even if I think it’s an overrated marriage of flesh between C and OCaml, Code of Conducts are generally a good thing, and the people who really like toxic callouts arre more of an anomaly, and likely were flown there due to the culture war stuff.
People hate rust because of its fences/training wheels, not because it’s “woke”
…actually I just saw someone in this very comment section ranting about “soydevs”, you’re not wrong. But there are valid complaints too! Some of us are just old and think our computers should do whatever we tell them up to and including “shit yourself and catch fire”
I agree with this, but I think rust is fine here. It has
unsafeas a keyword that let’s you do the breaking stuff, it just makes sure you know you’re doing something dangerous and makes it stand out for code reviewersThat’s why I prefer D’s approach for memory safety. Sure, it’s not as well featured as Rust’s, however it has “fat pointers”, three levels of safety, and kind of optional garbage collector.