I understand how you feel, this discussion is some...

# arrow

[pakoito]

I understand how you feel, this discussion is somewhat recurring. These terms already have years of documentation and literature, so changing the names now to Chainable would be the same as calling juice a Drinkable, or Slack a Chatable. While it makes sense in one bounded context, it wouldn't in others like juice brands or company registration. So we have the names they were given and we have to stick with them, making up better names for new constructs as we can, i.e. Defer and Async 😄

With that problem then it becomes a different perspective, we have to make people familiar with the terms by providing one intuition that works for them. Sadly not everyone reacts to the same intuitions, so we have to present the Chainable intuition, the burrito intuition, the "here are the tests" intuition, examples, etc... until they're understood.