I couldn't quickly figure out what sort of applications this person writes for a living. But for 95% of applications I can think of: whatever, you do you. Lots

I couldn't quickly figure out what sort of applications this person writes for a living. But for 95% of applications I can think of: whatever, you do you. Lots of people have pointed out flaws in his arguments here. There are always at least two collaborators on a codebase: you and you in two years time. You can enforce your own documentation best practice, but it's always possible to make mistakes unless you have a probably correct way of enforcing those best practices. I'm sure there are other very valid criticisms. But in the end, there's a good chance that 100% guaranteed memory safety actually doesn't matter for the software that write. If you told me this person writes software for pacemakers or ABS systems or something similarly safety critical I'd take issue. But beyond that it's a sliding scale from merely irresponsible to an inconvenience.