Address observables less obliquely
domenic opened this issue · comments
The section titled "observables" just serves as in introduction to signals, variables, and behaviors. It does not discuss the prevalent concept of observables from Rx in its various languages. From what I can tell, a Rx-style observable is something like a signal. Perhaps just use that name?
I need to do another pass on that to axe the term "Variable" in favor of "Behavior" entirely.
I think Signal and Observable have the same relationship as Deferred and Promise. We have made pains to avoid having to name Deferreds, with the revealing constructor. This morning it has occurred to me that when push comes to shove, we could use the revealing constructor for all of these and have a very output-centric view of the world, and that would probably be good. But for the purposes of this article, it is useful to name and illustrate each analog of getter, setter, and value.
Ah yeah, that makes sense. And I agree that for the purposes of the article it is helpful to have names for them all, along with code-entities you can manipulate. I would be curious how an output-centric view ends up, ergonomically.