I second that sentiment. That's probably also why, IMHO, more effort should be put into creating integrated introspection tooling beyond the debug node. But again, those efforts make the editor more of a "dashboard" - dashboard being something implicitly linked to the running system rather than being - as it is now - a static representation of what is happening on the server.
Along these lines, there is an idea of creating a running update of the context --> Streaming changes to context (NR5?) Which would also fall under the "dashboard" category.
I would love to be a fly on the wall and find out why all these "dashboard" features aren't being embraced. It makes Node-RED a far better tool for general purpose applications.
Ironically, for me, Node-RED isn't a "dashboard" nor "editor", it's just a fancy vector image editing tool. Unfortunately the shapes are limited to rectangles and lines connecting them but still just an image editing tool (built for the browser using jQuery).
