Rick Waldron (2013-12-18T03:30:37.000Z)
On Tue, Dec 17, 2013 at 10:17 PM, Shijun He <hax.sfo at gmail.com> wrote:

> You may not care about IE8, but many developers in the world MUST care
> about it.
>
> What I suggest is to help ES6 be faster to adopt, you know most team in
> companies are conservative to edge tech, that's why we need es5-shim or
> es6-shim projects.
>

Right, and map["delete"](key) works fine. The future of the language itself
should not be impaired by a browser that has an expiration date.



> It's too bad to write map['delete'], and you can't force all module
> authors write like that. Tools are helpful, but as Andrea point out, many
> tools are broken on reserved word up to now.
>
> And I think "remove" is a better name because Java/C# collections all use
> it.
>
> In fact, I don't care about whether it name remove or del, but just dont
> name it "delete", such name just trouble the developers who want to migrate
> to ES6 step by step.
>

The proposed collection APIs have been public for _years_ with a delete
method. It's really not as bad as you're making seem, please be objective.

Rick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20131217/07046bcf/attachment-0001.html>
domenic at domenicdenicola.com (2014-01-03T15:08:26.178Z)
On Tue, Dec 17, 2013 at 10:17 PM, Shijun He <hax.sfo at gmail.com> wrote:

> You may not care about IE8, but many developers in the world MUST care
> about it.
>
> What I suggest is to help ES6 be faster to adopt, you know most team in
> companies are conservative to edge tech, that's why we need es5-shim or
> es6-shim projects.
>

Right, and `map["delete"](key)` works fine. The future of the language itself
should not be impaired by a browser that has an expiration date.



> It's too bad to write `map['delete']`, and you can't force all module
> authors write like that. Tools are helpful, but as Andrea point out, many
> tools are broken on reserved word up to now.
>
> And I think "remove" is a better name because Java/C# collections all use
> it.
>
> In fact, I don't care about whether it name remove or del, but just dont
> name it "delete", such name just trouble the developers who want to migrate
> to ES6 step by step.
>

The proposed collection APIs have been public for _years_ with a delete
method. It's really not as bad as you're making seem, please be objective.