It seems to me that once again early adoption of non complete standards
wins in the short term, compromising the long one "forever" ...

Although IE11 promised incremental updates too and create an alias on the
global scope is not the end of the world, IMO.

We are all use to write abominations such `var url = window.webkitURL ||
windows.mozURL || windows.URL` and similar stuff all over, the reason
utilities libraries are often preferred, so while I am very happy that IE
team finally has been able to catch up and be even in front of other
browsers, I do believe that incomplete specifications or those still under
discussion should be adopted with prefixes until finalized in their form in
order to promote less mistakes in the long term.

And yes IE team, the prefix would lowercase as any other Browser is doing,
thanks.

Just my 2 cents.

Best Regards


On Mon, Dec 16, 2013 at 9:23 AM, Mark S. Miller <erights at google.com> wrote:

> Brendan and I had a side conversation the next day we should have brought
> to the attention of the group. In the main discussion, we said we needed to
> hear back from Luke, since "WeakMap" had already shipped in IE11. The next
> day we did, and Brendan & I agreed to drop the renaming. Which,
> fortunately, is also in agreement with Arv and Rick. WeakMap / WeakSet it
> is.
>
>
> On Mon, Dec 16, 2013 at 12:16 PM, Rick Waldron <waldron.rick at gmail.com>wrote:
>
>>
>>
>>
>> On Mon, Dec 16, 2013 at 11:59 AM, Erik Arvidsson <
>> erik.arvidsson at gmail.com> wrote:
>>
>>> At the last f2f2 we talked about renaming WeakMap to SideTable. We
>>> postponed the discussion, saying that we would get back to it later. We
>>> never did.
>>>
>>> I would like us to keep the name WeakMap as it is. We didn't really take
>>> WeakSet into account. If we rename WeakMap we would need to rename WeakSet
>>> too and I like the current Map/Set analogy.
>>>
>>
>> I'll second this with the added comment that after four weeks, SideTable
>> doesn't sound any better or worse than WeakMap.
>>
>> Rick
>>
>>
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
>>
>
>
> --
>     Cheers,
>     --MarkM
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20131216/807146d3/attachment.html>

It seems to me that once again early adoption of non complete standards
wins in the short term, compromising the long one "forever" ...

Although IE11 promised incremental updates too and create an alias on the
global scope is not the end of the world, IMO.

We are all use to write abominations such `var url = window.webkitURL ||
windows.mozURL || windows.URL` and similar stuff all over, the reason
utilities libraries are often preferred, so while I am very happy that IE
team finally has been able to catch up and be even in front of other
browsers, I do believe that incomplete specifications or those still under
discussion should be adopted with prefixes until finalized in their form in
order to promote less mistakes in the long term.

And yes IE team, the prefix would lowercase as any other Browser is doing,
thanks.

Just my 2 cents.