console.assert throwing behaviour and Console object

[qfox]

At the moment we have DeveloperToolsWG document about Console object (console.assert) and it's quitely strange to have different behaviour for console.assert in node environment.

Method console.assert was introduced in the early state of node development in 2010 via process.assert: 8e9f59a.

But now, when we very close to have document for Console object... What you think about fix console.assert behaviour in the next major release to stop throwing? And even fix all Console object methods?

[evanlucas]

It would be a breaking change (which isn't necessarily a bad thing). If this is something you feel strongly about, the best course of action would be to submit a pull request. Thanks!

[vkurchatkin]

I wouldn't object this change, but in general there is no goal (yet, at least) to make node's APIs fully compatible with web counterparts

[qfox]

@vkurchatkin Yeah, that's why I've come. ;-(

[jasnell]

A PR would be worthwhile. No guarantees it would land but it's worth opening the discussion.