IntlShim and Intl names may be exchanged.

[clmath]

I think it is more natural to require Intl if you want to pick any available Intl implementation (ie: the one from the browser or the polyfill) and to require IntlShim if you specifically want the polyfill.

[JCEmmons]

Perhaps you might be correct, but it also brings into question how much we trust the various browser implementations. One of the reasons we put this package together in the first place was to offer a somewhat complete package of locales ( at least one that would meet all of IBM's requirements ). So in that type of situation, we would want Intl = the polyfill. At least by doing so, we can guarantee consistent behavior across the various browsers.

I'm not inclined to change it at this point without a really good reason.