Immediately evaluate reactor.observe about nuclear-js

[jordangarcia]

I ran into this same issue when implementing a data-binding layer between Nuclear and VueJS.

Your solution of immediately evaluating and then observing is what I ended up doing.

In terms of leaking memory, i've found it best to not use reactor.observe many places but instead build it into a UI framework or conventionalize around some lifecycle of obsevation, ie a React Component.

By relying on observe as a way to read data from your system you lose a predictability and understandability of NuclearJS. In fact we have built an entire frontend and only use observe outside of a component binding maybe 3 times.

[jordangarcia]

The pattern you mention above @appsforartists seems like a pretty easy way to do this.

Having to evaluate before observe isn't a huge cost to incur and if we coupled evaluate with observe you could never get the behavior of "observing without first evaluating" without a flag passed to observe.

For now I am going to keep the API as is, since we are in 1.0.x