It's sometimes desirable to expose native platform functionality to the Ecmascript engine. This is typically done by adding a binding to the global object e.g. JSON and ByteVector.
This leads to the issues of namespace collisions and if the new native object should be universally accessible by all scripts. Could a ECMAScript module proposal cover 'native modules' - which are built into the platform (ECMAScript engine and browser) - and can be imported if required and are not a binding on the global object. Could be useful for vendor specific innovation.
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
