Joseph Savona

It's great to see people experimenting in this space and with the ideas of Relay. > To be completely honest I'm not even certain whether Promises alone are sufficient. A...

> I'm still imagining ways to properly and if possible declaratively annotate Promises-as-queries I'm curious what you come up with here. We found promises and URIs to be insufficient, hence...

@primozs Observables have the same problem as promises, they represent _opaque commands_. See [Thinking in Relay](http://facebook.github.io/relay/docs/thinking-in-relay.html#fetching-data-for-a-view) for more details on why Relay describes queries _as data_.

> I think Relay with GraphQL can take advantage of performing child fetches and transformations in the initial request. @tejacques Yes. Relay supports fetching all of the data for an...

> you may want to be able to batch data requests more intelligently than all-at-once, and render and stream everything to the client as soon as it is ready. I'm...

> The only issue with Relay2-style experimentation, compared to having stuff like this in the spec, is that it breaks the GraphiQL experience completely. @stubailo The same is true of...

> So perhaps the ideal world would be where the Relay query transformation was open-sourced as a separate tool so that the whole ecosystem of possible tools, including GraphiQL, could...

@dschafer Already covered the main variations of this, but I'll add a bit more detail about how we're thinking about variables in Relay2. We've found that the encapsulation provided by...

I’m no longer actively involved in development of this library but aligning w the RxJS api makes sense. When we first wrote the Flowable library, RxJS and the Observable spec...

Thanks for the detailed response! It's still a bit unclear how to resolve the original issue while also preserving the benefits of Cycle's approach (intents are really elegant!). It seems...