Personally, I don't like it. The options are: use a wrapper function (like you're doing) or use an uglier but familiar function. I feel like using a wrapper function is a higher cognitive overhead than simply taking more time to understand what's going on with `setTimeout` syntax: with a wrapper function, I need to find the function definition (and because this is Javascript/Coffeescript, it could be *anywhere*), read it, understand it (as well as understand *why* it exists), and keep that in my head while I'm reading through the rest of the code. By contract, with an ugly but familiar syntax, I have everything I need to understand the code right there in front of me: it might take me a bit longer than I'd like to understand it, but not as long as what you're doing here with `plantTimeout`.

Note that this argument gets flipped around if your wrapper function becomes familiar, itself. If we were already using this everywhere throughout the codebase, then I don't need to look it up because I'm familiar with its function and why it exists, and you're right that it's a cleaner syntax for Coffeescript. I'd suggest that you just use `setTimeout` here, and if you want to, then you can make a separate pull request where you go through a bunch of the code and replace `setTimeout` with `plantTimeout` all at once -- that way, it's easier to see the benefit of such a change, it can be discussed and considered in isolation, and if it goes in, then it gets used frequently enough to become familiar.