Discussion threads start at:
This issue was discussed again in the TC39 meeting January 2012, and the consensus was that the Internationalization API shouldn't become dependent on a module system that's not fully defined yet. We'll therefore stick with a namespace object.
Globalization seems too long to many, and it appears the name was also used in the global namespace by an early version of the library now called Globalize, so we switched to Intl.
The change from Globalization to Intl is included in the spec draft of 2012-02-23.