Initial Development

Browserify actually comes with an emitter:

https://github.com/substack/node-browserify#compatibility
https://www.npmjs.org/package/events-browserify
http://nodejs.org/api/events.html#events_class_events_eventemitter

The problem with doing it on the DOM element is that it's going to ultimately lead to some duplication of the selector. It's just much cleaner to listen to the instances. I rather use:

```
subscribe.on('subscriptionSuccess', callback);
```

... than:

```
document.querySelector('.subscribe-email').on('subscriptionSuccess', callback);
```

Course jQuery or a simple alias can get that on more equal footing, but it's even longer still! Also for something like an API response this is more appropriate than a DOM event, which are otherwise all about handling user interactions and user-facing browser features.