Comments by "" (@diadetediotedio6918) on "Zig is FASTER and SAFER than Rust | Prime Reacts" video.

This is not strictly true lol, even in insecure mode Rust's borrow-checker still exists, and there are parts of the code where naturally insecure patterns will arise when we are dealing with layers closer to the hardware, it has nothing to do with how consistently secure a language is, but how generally secure it is.
25
In virtually any real-world scenario, unsafe code in Rust will be restricted to strictly extremely low-level matters like communicating with the hardware or doing some operations that would be impossible in everyday language. We can quote here on the issue of the benefits of the approach of creating security wrappers in Rust to interact with unsafe code Asahi Lina herself, who has already said quite clearly how much the borrow-checker (which by the way exists in unsafe scopes also in some level) and the compiler in general made her experience of developing the M1 GPU driver much less complicated and more pleasant than it would have been without these features on other languages. So, IMHO, if you're using this much unsafe code like this you've probably already started off on the wrong foot in what your code should be.
13
@taragnor Hmmm, I think the last part is wrong, because we say "rewrite in Rust", and not "copy-and-paste in Rust", so it is expected that you would have some work redoing some things in the language instead just redoing the same thing.
6
 @OnFireByte Real mans do use punched cards, this assembly is a soy-boy way to program!
5
The compiler ensure some of the borrow-checker rules in unsafe Rust too, just not all of them or too strictly. Also, the syntax and tooling are great IMHO.
2