No browserify

I love browserify, but, in this case we gain very little from forcing our API to use it. 
Infact, I'd wager that for many use cases, the user might not even need the `Buffer` API for what they intend to use the decode for.
Therefore, IMHO, it is better to put that responsibility on the user and just give back what we are working with internally, an `Array`.

This would require a version bump to `2.0.0` though.
@jprichardson thoughts?