More words I wish there were

[simont]

Words for similar but distinct concepts, that are not themselves similar. The ELF standard for object and executable files contains two concepts which are similar enough to confuse, but different enough that it's normally important not to confuse them, and they're called ‘section’ and ‘segment’. I often wish they'd been called by more obviously different names: ‘section’ and ‘kangaroo’, or something. And I was just reminded this morning of another similar case: ‘project manager’ and ‘product manager’ as distinct corporate roles.

If two concepts are similar but distinct, the words for them should not reflect this by also being similar but distinct! They should be as different as possible.

Moral versus probabilistic ‘expect’. This might fall into the same general category as yesterday's moral vs tactical ‘should’, though I'm not sure whether ‘probabilistic’ and ‘tactical’ are similar enough for it to count. But even if so, it's a particularly noticeable sub-case of it and worth mentioning in its own right.

Imagine a parent saying to a child, before going to visit someone for the day, ‘Now I expect you to be on your best behaviour’; and then, when the child has left the room to get ready, they turn to their co-parent and say ruefully ‘I expect him to throw a huge screaming tantrum, so we'd better be ready to leave in a hurry’. Two clearly distinct words for ‘expect’, please!

Comments

[simont]

Perhaps "moral" wasn't quite the right word, but the sense I'm stretching for is "I will be outraged if it doesn't happen", as opposed to "I will be surprised if it doesn't happen".

[meihua.livejournal.com]

Yes, and that first sense is just an abuse of the second in the way that I described. It's a passive-aggressive guilt trip.

[simont]

Only in some scenarios. I still think they're perfectly good concepts, and not so awful as to be denied words to describe them by.

In particular, the two senses of 'expect' can perfectly well come up in cases that have no guilt-trip dimension at all. Network protocol design, for example: a server might expect{1} its input to be well-formed (and is justified in abandoning the entire connection if it isn't), but expect{2} 99% of its input to consist of the three most common requests (and therefore implement a fast path to provide cached answers to those three, but must still contain the more general code that handles the remaining 1% of cases correctly).

Hmm, that example makes me think even more that "moral" was a poor choice of word on my part, but I'm not sure what should best replace it...

[meihua.livejournal.com]

Fair enough. I think the interpersonal use you described is a third, emotionally manipulative case.

[wildeabandon.livejournal.com]

I don't see what's passive-aggressive about it. Telling people that a particular behaviour will outrage* you sounds like fairly straightforward boundary setting to me.

*or upset, or disappoint**, or whatever
**generally what I would mean by "I expect you not to do this" if I don't mean surprise