For a preview of the future, try this one on macOS 10.12 today:
% lldb --one-line run /usr/bin/python
spoiler:
Current executable set to '/usr/bin/python' (x86_64).
error: process exited with status -1 (cannot attach to process due to System Integrity Protection)There is a genuine argument about control but overselling it just lowers your credibility, especially since it reveals tunnel vision: statistically very few Mac users need to run a debugger but more are at risk for malware which uses sensitive APIs.
Also, if you have malware getting far enough to try to ptrace binaries running on your uid, I would imagine things are still game over despite being prevented from debugging a new interpreter process. I'm not buying the malware scare when it comes to debugging newly forked processes on a non-root uid.
I think your argument would have been valid if I'd never clicked "enable debugging for this mac" in xcode.