Jake Verbaten

Well an easy solution is rework the UI so that the expore features stuff becomes a sidebar. Or use a `` for the explore features stuff (with a shim ;))...

Defiantly worth mentioning. Neiter appear to be polyfills they are just feature equivelant emulation using propietory APIs. Writing a real polyfill shouldn't be too difficult though.

That's not what I meant. I meant the polyfills don't use the native API. (the polyfills use their own propietory API, except the term "propietory API" is poorly used to...

Would firing visibilityChanged events through an emulated DOM2 events (`addEventListener`) API in oldIE count as a 100% polyfill? That should be possible. Also DOM 0 event listeners like `document.onvisibilitychange` should...

The following polyfill : https://gist.github.com/1677020 given some polish and testing should work correctly. Note that legacy browser support in this case requires polyfilling `addEventListener`, `[].forEach` and `Object.defineProperty` which should all...

Its worth mentioning yes, not sure what I would write about it, may get around to it.

We've not implemented `Null`, `Statsd` or `Prometheus` yet for the cached stats reporter. For testing purposes I will need to use use `Statsd` and `Null` reporters soon, I can contribute...

Actually, every counter, gauge and subscope allocated is another iteration in this loop ( https://github.com/uber-go/tally/blob/master/scope.go#L157 ). The array of subscopes is unbounded if sub scopes are allocated dynamically and there...

Interesting. Can't trust those browsers :(. Good job on the whole making it spec compliant thing though o/

Augment.js - implements only the _fully shimmable_ subset of ES5 - has a single file for every shim method ES5-shim.js - implements the fully shimmable subset and the partially shimmable...