| First of all, enable/disable is a dichotomy, and is not a set of two dichotomies. Second, imagine an editor that has AI running in the background, scanning your files. "Enable_AI" could just mean enable the visibility of the feature to actually use the results. On the other hand, it would sound more suspicious if there were some background AI tasks running, even for training purposes, if "disable_AI" were "True" as compared to "Enable_AI" to be false. In other words, Enable_AI COULD have the connotation (to some) of just enabling the visibility of the feature, whereas Disable_AI gives more of a sense of shutting it off. Imagine for example you're in a court of law. Which one sounds more damning? =======
Prosecutor: You still have AI tasks running in the background but AI_Enable is set to false? Defendent: But Enable_AI just means enabling the use of the output!
==== ====
Prosecutor: You still have AI tasks running in the background, but AI_Disable is TRUE? Defendent: Uh....
==== |
Personally, I don't feel much difference between the two. I doubt that an average reasonable person would either.