Consider making W3C complient objects NativeObject instances

Right now our implementations of W3C APIs like console, XHR, worker, websocket, etc. are (almost) a strict subset of the official standard. This is good for compatibility, but:
* it holds us back from adding new features that may not make sense in the browser.
* It also makes app code appear inconsistent, as the APIs for event handling are very different from our event API.
* It splits our API documentation in to two different groups, handwritten articles/type declarations, and the documents generated from our .json files.

However, I'm really reluctant about this.
* We then have two completely different event APIs on the same object, but only on some. (Actually three, considering the `onfoo = cb;` APIs from ye olden days.
* There is the chance of API clashes with future W3C APIs.
* ~~As a matter of fact, we already have a clash on localStorage with the `set` method.~~ I was wrong about that, it's actually `setItem`.

Please discuss.