On Wed, Dec 18, 2013 at 1:55 PM, Rick Waldron <[email protected]>wrote:
> > Submit patches—libraries intended for use in IE8 should be made to support > that platform, it's that simple. > Submitting patches is irrelevant and impractical here. Why use es5-shim? Because we want to use some scripts written in es5 WITHOUT asking the authors change their code. Though sometimes es5-shim is not enough (for those rely on getter/setter syntax or Object.create(null) which hard to shim). What I'm talking about is: there will be many modules using ES6 API but still can be used in ES5 or pre-ES5 or even pre-ES3 environment with es5/es6 shims (if they do not rely on the complex features like Proxy or Generator). So bordering the original authors to change their code from a.delete() to a['delete'] are meaningless and I don't expect they will accept such "patch". (Do anyone really think change a.delete to a['delete'] is a patch?) > > Wrong—that impairment has nothing to do with browsers, but with > _existing_ code that makes incorrect assumptions (or none at all) about the > return value of typeof. > I don't see any difference here. Whether it's correct or incorrect assumption, the spec can not change that behavior. In my opinion, using reserved words as methods name in standard library is far more problematic than the case of typeof null (because I don't know any real product code rely on typeof null === 'object' and if any it's very easy to fix).
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
