If all prefer this I'll capitulate. But to me that requires the reader to go read the function's code and grok internal Bacon details to understand what it does, whereas `leafletEventStream()` is likely to be immediately understood. 

We could have both functions in BaconUtils, have my name call Justin's name, and use my name in calls as currently.

Adam points out that perhaps best is to integrate it into Leaflet like Justin did for OpenLayers so we can just call `asEventStream` on the object.