Part of the attraction of Visual Programming is the instant feedback derived from adjusting a value input to a node.
An edit might be as simple as adjusting the X position of some text. Opening up demo comps and making adjustments to node inputs to get a sense of how they work I am frequently frustrated by the need to restart the composition just to see the adjustment rendered. If the node could just be made to fire as one adjusts values one could see what's happening — the essence of visual programming. The work around seems to be to wire up a machine gun trigger node (Fire on Window Refresh) into the patch I'm working with which is pretty boring to have to do repeatedly. (I guess if the Editor was scriptable one could assign a hot key to a script to do this).
There could be a pref for either fire when enter key is pressed to input a value or to fire every time the up/down arrows or a value that makes sense is inputed (i.e. if it's a number input an accidental alphabet character would not cause it to fire just input values that check out on first parse of input). This would differentiate between constant feedback and slightly less feedback but more than we get at present.