Re: Advice on EventStreams vs. Observables Proposal

On Wed, Nov 12, 2014 at 4:09 PM, Arun Ranganathan <arun@mozilla.com> wrote:
> Currently, the evolving FileSystem API[1] makes use of a placeholder host
> object called an EventStream[2], first proposed in a post by Tab Atkins. It
> lacks a formal specification, though.
>
> The question is, where should such a concept be specified? I’ve tried to see
> what became of TC39’s Observables idea (which shares some naming simiilarity
> with Object.observe(), unfortunately, but might be the logical next step for
> ideas like EventStream), but I couldn’t find anything, which leads me to
> believe it hasn’t quite made the cutting board (and I’m imagining TC39 is
> pretty busy these days).
>
> There may be advantages to this being a host object, particularly since use
> cases like the enumerate function in the FileSystem API are already early
> adopters, even if that’s wishful thinking. I’m willing to write the
> specification for it, with semantics similar to Tab’s original proposal [2]
> (which are unlikely to stay exactly the same). But if TC39 is working on
> something, I’d love a pointer to it, and that’s why I thought I’d check in
> with those that subscribe to this listserv.
>
> Feedback strongly encouraged! And I’m sorry if I’ve missed a TC39 proposal
> after all; if such a thing exists, a pointer would be invaluable :)

To the best of my knowledge, object-based streams aren't yet being
worked on in TC39.  Domenic would know better, but last time I talked
to him, he was only dealing with binary streams (the Stream
interface).

I'm very happy to help with developing a decent object-based stream
interface, which has very different constraints than binary streams.
A lot of work has happened in the last few years in the reactive JS
community exploring this space, and it would be great to get something
into JS that embodies some of these ideas.

~TJ

Received on Thursday, 13 November 2014 00:17:06 UTC