geval vs observ about mercury HOT 4 CLOSED

alternatively

var Event = require('geval/event');

module.exports = Observable;

function Observable(value) {
    var event = new Event();
    value = value === undefined ? null : value;

    observable.set = function (v) {
        value = v;
        event.broadcast(v);
    };

    return observable;

    function observable(listener) {
        if (!listener) {
            return value;
        }
        return event.listen(listener);
    }
}

from mercury.

geval and observ represents different data structures.

geval represents an immutable series of discrete events. Once you have a geval instance all you can do is listen to events.

observ represents a mutable value over time. Once you have an observ instance you can ask it for its current value at any point, you may mutate it and you may listen for changes to the value.

This distinction is based on FRP literature.

For example note the computed() function in observ. It does not make sense to create a computed event (because the answer to "whats the current value" of a series of discrete events is not defined).

In the future both geval and observ may have other higher order functions that only apply on themself.

from mercury.

ok, but what about my alternative implementation that uses geval to implement observ? the current semantics are unchanged with this but it has the benefit of removing duplicated code? events and behaviors are still distinct but we leverage code reuse.

from mercury.

@neonstalwart We could use geval in observ.

However that saves a few lines of code and makes observ harder to read. observ currently is a zero dependencies module. I think it's easier to reason about as is on it's own.

from mercury.