#flowbasedprogramming — Public Fediverse posts

"Nothing will ever be attempted if all possible objections must first be overcome."
-- Samuel Johnson

This talk, "A World Without Apps" with Michel Beaudouin-Lafon, is yet another talk that makes me feel all inspired and start thinking about the inherent composability and potential for unanticipated reuse of #FlowBasedProgramming components.

The talk is all about how we are increasing complexity and raising the walls of the silos, and how sending a file to your friend is _harder_ than it was.

invidious.snopyta.org/watch?v=…
www.youtube.com/watch?v=ntaudU…

/via malleable.systems/catalog/
/via ponies.im/@Gnuxie/105975258060… @Gnuxie

#MalleableSystems

Running into issues with #AirFlow and sub-DAGs, and now I'm reading about #CommonWorkflowLanguage and #WorkflowDefinitionLanguage and wondering how they map onto #FlowBasedProgramming.

I'm having the same issue as Twine was having over at web.archive.org/web/2019091209… which I suppose I could solve the same kind of brute-force way they did, but it's easy to start diverging into more research.

I'm looking at Toil(0) and Arvados(0) and what they can do.

(0) toil.readthedocs.io/
(1) arvados.org/

I strongly suspect we'll end up just not running a workflow engine down the road. Our use case is not super complicated, but the workflow engine integration is turning out to be. The whole flow status monitoring UI *is* nice to have though.