Lack of integration with jQuery

[legalbox]

The Globalization plugin defines methods, both public and private, that are already part of jQuery:

• Globalization.extend() -> jQuery.extend()
• trim() -> jQuery.trim()
• isArray() -> jQuery.isArray()
• isObject() -> jQuery.isPlainObject() or jQuery.type(obj) === 'object'
• arrayIndexOf -> jQuery.inArray()

Is there something specific in these implementations that prevents calling jQuery methods instead?

[scottgonzalez]

There's nothing jQuery-specific about the globalization plugin and the benefit of providing something that works everywhere outweighs the benefits of not defining a few small functions.

[jzaefferer]

There actually was a jQuery-independent version of the plugin, exporting window.Globalization. I removed that, as it duplicated the full plugin and made any changes require changing two files.

What we actually need is a build that exports a jQuery-free version. And the jQuery-specific version could be optimized to use jQuery methods, but the overhead is pretty small, so not so much of a priority.