My experience crafting an interpreter with Rust

> The rules are simple but for some reason, it’s really hard to keep track of them in a big system.

I think this still applies to working with pointers in C, the outcome is just different when you get them wrong :)

This post was wonderful though. Very honest and nuanced. It's interesting to hear that even in a "toy" project, the author was forced to sprinkle in some unsafe { } to get performance comparable to C. But I don't think this is the indictment it sounds like: it's possible that strategic use of unsafe { } is just an unavoidable part of writing high-performance Rust, and that the language's main value lies in encapsulating and bridging those parts. It seems like ASM is often necessary in high-performance C code, yet we still value the C that covers all the space in-between. I think having 95% or 70% safe code is still very valuable.

Thanks for the post. An enjoyable read.