Observables in and out

[mlajtos]

Description

In Observable-based interpreter, every function takes a raw JS value and returns an Observable. This breaks composionality and it is a bad design choice.

This problem complicates/prevents implementation of following functions which were trivial in Promise-based interpreter:

• Flow (old implementation)
• Gradient (old implementation)

Solution

Obviously, every function should receive and return an Observable.

Consequences

• function can decide on how to combine the Observables (via operators)
• simple functions can be easily lifted to an Observable ones
• every value the interpreter sees is an Observable (object === Observable of object containing Observables? whoa, ble, haha, hmm :D)
• there can be (syntax) operators and functions for Observable operators
• proper Flow implementation (and others constructs)
• implementation of functions will be verbose (unless they are not automaticaly lifted)
• Mouse.x * 10 should work right away
• one can lost very easily in a higher-order Observables
• What will function application do?
  • combineLatest should get two second-order Observables (?)
  • therefore Interpreter should manipulate only second-order Observables (?)
• ...
• more to think about..