>> I don't think sharing a prefix/root implies that they're the same thing.
I think the complaint is that the the shared prefix/root causes the two words to be less distinct from each other
>> For example, when exactly do you "login" when calling an API with a bearer token? Doesn't work for me.
In my mental model, you "login" to the API when you provide the bearer token.
While I would agree that this is "stretching" the meaning of the word login quite a bit, passing the bearer token serves the same functional purpose as a human keying a UID / PW combo.
In an activity where words have specific meanings and should be used in their correct place in order to prevent miscommunication of intent or purpose, "stretching the meaning" of a particular technical term can only bring confusion (and bugs).
Authentication and Authorization are correct and complete terms that have separate but related meanings, personally I don't feel them to be confusing at all.
The entire article feels like whining because the author stubbed his toe against a corner.
Lay people need explaining these concepts using non technical words? Of course, that's what documentation and manuals are for. "WE" are not lay people, and we should understand what their meanings are.
I think the complaint is that the the shared prefix/root causes the two words to be less distinct from each other
>> For example, when exactly do you "login" when calling an API with a bearer token? Doesn't work for me.
In my mental model, you "login" to the API when you provide the bearer token.
While I would agree that this is "stretching" the meaning of the word login quite a bit, passing the bearer token serves the same functional purpose as a human keying a UID / PW combo.