Deprecating Future's .then()
Mark S. Miller
erights at google.com
Wed Jun 5 07:17:06 PDT 2013
We are arguing about enough other issues that -- since this seems to be
controversial as well -- to avoid an avoidable argument, I will include all
three lists as you do here. However, for the record, I think this is silly.
There's nothing about this issue that is browser specific. The fact that it
is currently "implemented above the language-level", meaning I assume the
language implementation, is irrelevant. Many linguistic abstractions are
implemented first as libraries. This is a victory when it happens, as it
means the underlying abstraction mechanisms were sufficient. Over time,
some elements of some of these libraries become blessed as part of the
language. This is as it should be.
What about any of this is specific to the browser is beyond me.
On Wed, Jun 5, 2013 at 3:17 AM, Anne van Kesteren <annevk at annevk.nl> wrote:
> On Tue, Jun 4, 2013 at 4:42 PM, Mark S. Miller <erights at google.com> wrote:
> > I just realized that this thread has occurred so far only on the wrong
> > lists. Please let's proceed from here only on es-discuss. This is a
> > issue, not a browser issue. Let's please stop splitting the discussion
> > between two communities.
> That's why public-script-coord is used, which includes both. And for
> now it's implemented above the language-level, so excluding those not
> subscribed to es-discuss as you did in your next emails is poor form.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss