I read that as “code written in a non memory safe language”, since that’s the nomenclature that memory safe languages use when they need to execute code that can’t have the guarantees the language typically enforces (often when interfacing with things outside their ecosystem).
And they should be. Software has become much bigger than it was "half a century" ago. We need to scale up on C.
> "unsafe" code is really not that bad.
Wow,... I only hope I never need to maintain your code.