W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2013

Re: Futures (was: Request for JSON-LD API review)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 17 Apr 2013 17:33:02 +0100
Message-ID: <CADnb78jqvFj0f0=ZOm3c5f0+z-Pzq-OJSP5d2zGkEEm0er5d7A@mail.gmail.com>
To: "Mark S. Miller" <erights@google.com>
Cc: es-discuss <es-discuss@mozilla.org>, Douglas Crockford <douglas@crockford.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Norbert Lindenberg <w3@norbertlindenberg.com>, Markus Lanthaler <markus.lanthaler@gmx.net>
On Wed, Apr 17, 2013 at 5:06 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
> [...]

My previous experience has been trying to get bytes in JavaScript
(mostly for XMLHttpRequest): asked from TC39 in 2006. Eventually
delivered by Khronos for WebGL. Mourned over by TC39 (and others,
myself included) in 2012. If the party "responsible" for delivering
the solution does not deliver, it will happen elsewhere. And to some
extent that seems good, as it keeps everyone alert and the platform is
not held hostile to the progress (and process) of a single entity.

As I mentioned elsewhere, the platform needs more primitives. IO
streams, event streams (or signals), futures, ... I have no strongly
held believes as to where these should be hosted, I just know that we
need them, soon. And getting them soon in JavaScript seems hard as
you'd have to lift up the event loop model defined in HTML somehow to
the language level.

Received on Wednesday, 17 April 2013 16:33:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:12 UTC