It would be a clear signal to anyone reading the code that they are dealing with an instance of Topologica.js, which is not necessarily clear if you come across dataflow in code somewhere.
It's less cognitive burden.
It follows the object oriented convention where instances are lower case versions of their constructors.
Cons:
It's a rather abstract name for the instance, but at least it makes it clear what it is. Is it a state? is it a dataflow? No, it's a topologica! This feels right, as the concept is pretty unique to this library. Although, it would be interesting to research what other libraries use for this term - the instance of the reactive thing.
Implements 4.0 Ideas #42
dependencies
toinputs
set
get
dataflow
instance into reactive functionsInterestingly, these changes reduce the minified build from 825 to 760 bytes.
Reviews welcome!