3 ms·
Side note: interactive debugging is kinda inherent with the flow based programming paradigm. The program is continuously executing with every new action and imm
by koolhaas 5y ago
Side note: interactive debugging is kinda inherent with the flow based programming paradigm. The program is continuously executing with every new action and immediately reflecting the current state. To program with it is to debug. If there’s an error with a component, it turns red and everything down stream breaks as well.
- taeric 5y agoThat falls on is face at scale. There is a reason not every bullet in a gun is a tracer bullet.
- koolhaas 5y agoFlow paradigm doesn’t claim scale though. It’s about being a DSL for specific environments, often visually-oriented software like CAD or interactive art, which doesn’t have heavy 10K person team requirements.
- taeric 5y agoFair. And I think there is more here. If you are programming a singular thing, this probably has good legs. As soon as you are programming many things, though? This is why cad systems can be seen as visual programming of parts, but are never considered for this debate.
- koolhaas 5y agoI’d be curious to hear you elaborate on the singular/many things point. Trying to understand which deficiency you are pointing out.
- taeric 5y agoFor example, Programming a security system for my house would be great visually. Programming all of the houses on my block? Not so much. Even though the textual rules would be roughly equivalent.
- hermitcrab 5y agoYes, I think that sort of instant feedback is very helpful and is probably one of the reasons Excel is so popular.