Memory safety is often misunderstood as separate from thread safety, but the author argues that both concepts are intertwined, emphasizing that absence of Undefined Behavior is the true goal. Using a Go programming example, the article illustrates how data races can lead to memory safety violations, pointing out that Go lacks the robust protections seen in languages like Java and Rust. Ultimately, the author advocates for a clearer understanding of safety guarantees in programming languages, particularly regarding the implications of Undefined Behavior.