The first example is a little hacky in using one function as both keyup event handler and message receiver. This and some other quirks together make things har

The first example is a little hacky in using one function as both keyup event handler and message receiver. This and some other quirks together make things harder to understand. The idea seems really cool, but a clearer (even if not as fun to read) README would help. :) If I were the maintainer, I'd reduce the amount of text (by moving extensive API docs somewhere else? cutting some of the stuff that is just-for-lulz?), and think of adding an overview—how coalesce fits among existing solutions. Yeah, dry and boring, but practical.