Should we adopt RxJS/Observables as a core design pattern?
They are like if you combined Events+Promises+Generators. Where Promises are either resolved or unresolved, and Generators require the consumer to request the next value, Observables sort of combine the two to make event based programming easier.
RxJS 5 is being rewritten and is done in TypeScript.
Reactive is a mature and widely-supported (across programming languages) library. Gaining the full benefit of using Reactive requires a fair amount of learning its paradigm and API, but one could also use it much like Dojo 1.x users currently use Observable, Evented, Promises, etc.
Reactive's mantra: Everything is a stream
Since the source is TS, I think it should integrate into our development and build process like any other TS dependency.
I think core/Evented becomes redundant
There is overlap with core/streams, but probably enough differences for both to be useful
Reactive's Observable has some utility methods (and a Symbol shim):
Reactive also has some scheduler support - TODO: compare scheduler between Dojo and Reactive
ReactiveX/RxJS Observables appear to be a good design paradigm. As @msssk points out, there are some additional activities we need to do in order to better integrate it. I will open other issues in relationship to this.