[jononor]

I agree wholeheartedly with being able to go inside the black-boxes, and the transition be smooth. In NoFlo, one of the the main runtimes for Flowhub, the components are JavaScript/CoffeScript|. They can be viewed and modified from within the UI. The API is pretty simple, and was improved further with NoFlo 0.5. I'm experimenting with some ideas from the functional and automata/finite-state-machine world on how we can improve things further. I also think it is important that people can freely chose how much and on what level you use text/code OOP and which level you use nodes/graphs FBP. Embed NoFlo as a DSL for a particular problem area, use as general purpose language, or just as a coordination layer between your high-level modules.

| In MicroFlo, another runtime for microcontrollers, they are C++