Choosing Globalization API namespace

Nebojša Ćirić cira at
Thu Nov 17 14:18:56 PST 2011

Looking at the

module i18n from '@Globalization'

is how modules are going to work in the future.

What you propose in the mean time is to define Object.system.load(...)
method (Latest Chrome doesn't have Object.system, so that would need to be
defined too).

The load method could return a reference to the hidden global object like:
var i18n = Object.system.load('Globalization');

In our case, we already have v8Locale global so load would:

Object.system.load = function(name) {
  if (name === 'Globalization') return v8Locale;
  return undefined;

Am I getting this right?

17. новембар 2011. 13.14, Brendan Eich <brendan at> је написао/ла:

> On Nov 17, 2011, at 10:07 AM, Nebojša Ćirić wrote:
> > HI all,
> >  we briefly discussed the i18n namespace at the meeting yesterday. It
> seems that "Globalization" (current proposal) could conflict with jQuery
> plugin, and also some members were worried about the actual name length.
> >
> >  Somebody mentioned we should wait for module implementation/spec to
> settle, but I don't think that would be reallistic if we were to start
> working on i18n API prototype(s) in the near future.
> Modules are being prototyped in the near future, so there's nothing
> drastically less realistic about depending on some spec draft provision. It
> could change, but you could also bootstrap it in JS and not even wait for
> the concurrent module system prototyping to get that far.
> >  What do you think would be a good alternative (Object system was
> mentioned, but I would need more deatails there)?
> No, that is the "use the module system" idea. We need to agree on how the
> system loader, or the system modules, are reflected into legacy script
> without injecting new globals. Object.system as the system loader reference
> is one idea. Then you might wire up Object.system.load("@g11n"...) or
> whatever the right module loader API is.
> /be

Nebojša Ćirić
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list