[DCoder]

> Can I possibly even start the discussion at why the hell these things are being named in this way?

This reminds me a lot of Perl with its creative naming for things, e.g. promises giving you a `Vow` object that you can `keep()` or `break()`. Or how you `bless` an associative array into becoming an object of a certain class.

On the one hand, it is good to have precise and specific terms without reaching for a thesaurus or overloading the same term (e.g. the many meanings of `static` in C).

On the other hand, if every framework and language invents its own terms for everything under the sun, that will not help polyglots or newcomers.

(On the third hand, we have foreigners trying to spot a difference between a "promise" and a "vow".)

Promises are my favourite example of this, because just between C++, C#, JavaScript, and Perl, I can find three-and-a-half different taxonomies for the same functionality.