You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this package is getting a fair amount of twitter and blog visibility, I'm concerned that some false expectations are being created. In particular, it isn't clear from the description of the project that it while it provides an ES5 compatible API but that it does not and cannot provide ES5 semantic extensions that are not already present in the "older" browser.
This shows up in all legacy browsers for functions such as Object.freeze and the inability to set property attributes. For IE<9 browsers it will show up as an inability to define getter/setter properties. User's of this package really should be warned of these limitations.
The text was updated successfully, but these errors were encountered:
Thanks, Allen. I didn't realize it was getting so much attention, although there have been a fair number of comments today; I haven't even written a README yet. I'll make sure to put up a sign post.
A concern:
Since this package is getting a fair amount of twitter and blog visibility, I'm concerned that some false expectations are being created. In particular, it isn't clear from the description of the project that it while it provides an ES5 compatible API but that it does not and cannot provide ES5 semantic extensions that are not already present in the "older" browser.
This shows up in all legacy browsers for functions such as Object.freeze and the inability to set property attributes. For IE<9 browsers it will show up as an inability to define getter/setter properties. User's of this package really should be warned of these limitations.
The text was updated successfully, but these errors were encountered: