3 ms·

Then surely the answer should be that there should be a config setting that disables it, with the option to do something like "WITH FORCE" which would force ena

Then surely the answer should be that there should be a config setting that disables it, with the option to do something like "WITH FORCE" which would force enable it in the environment even with that config setting enabled. This gives the best of both worlds, in that it stops people from copying blindly from Stack Overflow, but doesn't give the sense of security that it initially seems to imply.

btilly 3y ago
Yes, lots of people had ideas about this should work. Exactly like you just did. Unfortunately they had different ideas. And that's why there was months of debate over how this feature should work before something was accepted. Just to give one example of an obvious problem with your idea, saying "WITH FORCE" will suggest to some that this configuration setting is somehow forcibly maintained. This is likely to generate bug reports based on that misunderstanding. "I said WITH FORCE and it is easy to get around!" And, worse yet, questions about, "Why do we have a security feature that doesn't provide any security?"