> Never go full-Object-oriented programming. Agreed, but that wasn't what I was saying or replying to, was it? I was arguing that method implementation tied t

> Never go full-Object-oriented programming. Agreed, but that wasn't what I was saying or replying to, was it? I was arguing that method implementation tied to an instance isn't the type of thing people mean when they refer to tight coupling. Coupling is related to breakage/maintenance; when you touch this thing here, if it's tightly coupled with some other component, it will also require (sometimes unexpected) changes in that other component. Whether one should or shouldn't go full OO is an orthogonal consideration.