Re:Show HN: Riko – A Python stream processing engine modeled...
by beardicus on Thursday July 21, 2016 @01:23PM
(#12138440)
I don't feel like blocks really maps well to the kinds of tasks i'd do in node-red and yahoo pipes, and presumably riko (I didn't dive too deep here yet though). a wiring interface better reflects the idea of inputs, filters, and outputs, and wiring them up in flexible ways. blocks seems a little rigid and more variable/iteration/function-based.
maybe figure out a few common workflows that people would make in riko or node-red, and mock up how they'd work/look in blocks vs. wiring/pipes.
Re:Show HN: Riko – A Python stream processing engine modeled...
by reubano on Sunday July 24, 2016 @01:34PM
(#12153975)
> maybe figure out a few common workflows that people would make in riko or node-red, and mock up how they'd work/look in blocks vs. wiring/pipes.
Good idea, what are your workflows?
Which interface do you think is more newbie friendly? My gut says blocks (maybe something a bit more simple/refined than blocky) are easier to grok, while wires allow for designing more complex workflows.