The text doesn't go into detail, but I think the GP is right. You can model this as cooperative vs preemptive multithreading.
In a preemptive model, each process just does its thing until it gets interrupted by the scheduler, and then then that process does its thing until it gets interrupted in turn. This is the "church of interruption" model. Its the responsibility of the other (scheduler / person) to signal to you (via an interrupt) when your turn is over.
But in the cooperative multitasking model, its the responsibility of the speaker to hand the baton back. It is vulnerable to a single person / process dominating the whole space by talking / running forever. And this is totally what happens when the two cultures meet - I have a friend who is 100% church of interruption. I came back from a retreat feeling calm and peaceful. We talked on the phone for a few hours the next day and I patiently waited for him to be done before I replied - which took about 3 hours. He was vaguely confused / annoyed at me for doing that. Apparently it simply didn't occur to him that if he wanted to know my thoughts he might need to ask me for them.
In the cooperative multitasking world, the golden rule is that all programs should run for a short amount of time then yield back to the scheduler so it can run something else. Its not so cut and dry for humans - I think "speak briefly" is a lossy summary of the rule because it often makes sense for one person to do most of the talking in a conversation. But in the "strong civility" culture its the responsibility of the speaker to be aware of tracking that, and usually do so only with the blessing of the group. Taking all the air in the room is a faux pas.
In a preemptive model, each process just does its thing until it gets interrupted by the scheduler, and then then that process does its thing until it gets interrupted in turn. This is the "church of interruption" model. Its the responsibility of the other (scheduler / person) to signal to you (via an interrupt) when your turn is over.
But in the cooperative multitasking model, its the responsibility of the speaker to hand the baton back. It is vulnerable to a single person / process dominating the whole space by talking / running forever. And this is totally what happens when the two cultures meet - I have a friend who is 100% church of interruption. I came back from a retreat feeling calm and peaceful. We talked on the phone for a few hours the next day and I patiently waited for him to be done before I replied - which took about 3 hours. He was vaguely confused / annoyed at me for doing that. Apparently it simply didn't occur to him that if he wanted to know my thoughts he might need to ask me for them.
In the cooperative multitasking world, the golden rule is that all programs should run for a short amount of time then yield back to the scheduler so it can run something else. Its not so cut and dry for humans - I think "speak briefly" is a lossy summary of the rule because it often makes sense for one person to do most of the talking in a conversation. But in the "strong civility" culture its the responsibility of the speaker to be aware of tracking that, and usually do so only with the blessing of the group. Taking all the air in the room is a faux pas.