W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2013

Re: Standardizing console APIs: Where?

From: Brian Kardell <bkardell@gmail.com>
Date: Tue, 26 Feb 2013 17:06:48 -0500
Message-ID: <CADC=+jecvHXm5wsAZzRFcGQ9Djd0KuUyggKqH8iE25jS-3N+gA@mail.gmail.com>
To: Jorge Chamorro <jorge@jorgechamorro.com>
Cc: Marcos Caceres <w3c@marcosc.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Domenic Denicola <domenic@domenicdenicola.com>, "Hill, Clint" <clint.hill@goaaa.com>
It seems that I may have mixed a few assumptions from side conversations on
twitter/chat and been less clear than I could have been.

My question here was really a few fold:

1. Does anyone else feel like we _should_ have a standard
2. Given that this goes beyond the browser, where should that standard
live?  I feel like its proper home is ECMA since the API, again, has not
really anything to do with browser necessarily.
3. If ECMA, is it part of the language (ES7?) or is it separate like i18n?
 I was actually suggesting that my opinion is the later, this feels like an
ECMA module that could use standardization and is commonly imported in
browsers and many engines for back-compat as 'console' (though I suggesting
'logging' is a better API term).  I also suggested (in the strawman) that
it could start _very_ small with the abstract APIs that are at least
universally non-breaking (even if they might do something slightly
different) and have been fermented for years and years - thus it should
mostly be an easy approval to find a home and basis on which to gather
proposals and consensus

Those are my merely opinions and rationale - I am happy to be wrong on any
of them :)

Received on Tuesday, 26 February 2013 22:07:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:08 UTC