Moving String.prototype.substr to normative part of the spec
allen at wirfs-brock.com
Sat Aug 4 14:15:59 PDT 2012
On Aug 4, 2012, at 1:30 PM, Mathias Bynens wrote:
> On 3 Aug 2012, at 20:34, David Bruant <bruant.d at gmail.com> wrote:
>> I'm wondering what's the downside of adding it in the normative part of the spec. It's in every browser, it's in Node.js, it's likely to be in MongoDB JS (I haven't tested, but it's based on SpiderMonkey 1.7, and soon V8), likely in all the mostly used JS platforms (which are often based on browser-included JS interpreters).
>> It's likely that platforms that support ES6 without substr will suffer from interoperability from libraries/modules that use it and rely on it and will be forced to add substr anyway.
More information about the es-discuss