"If you're that confident in your knowledge here, then using Rust wouldn't be a problem for you: you can go the unsafe route and just do the same thing you'd do in C."

That's what I didn't understand - why the author didn't just use "unsafe". There's nothing intrinsically bad about using "unsafe", you just have to test that code thoroughly. There's plenty of robust C code out there.