RE: Standardizing console APIs: Where?

On Monday, February 25, 2013 at 09:54, Marcos Caceres wrote:

> _However_, if evidence of interoperability issues can be presented, and those are causing developer pain, then that makes for a stronger case for standardisation.

One case of pain I've seen is that in some browsers, `console.log` is bound to `console` (Firefox and Node.js, that I know of). Whereas in others, it is not (Chrome, that I know of).

The former behavior is much more convenient, and allows writing code like `array.forEach(console.log)`. However, such code is not portable across runtimes, as in the ones without a bound `console.log`, it fails with some cryptic error message.

Standardizing on bound versions of the functions would be nice!

Received on Tuesday, 26 February 2013 06:28:57 UTC