#flowbasedprogramming — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #flowbasedprogramming, aggregated by home.social.
-
New #sideproject idea: an #EmbeddableScriptingLanguage (kinda like #Lua) that is designed for #FlowBasedProgramming.
The key thing for me is having an easy way to see which outputs depend on which inputs.
And the easiest way to do so would be with an embeddable language that could transform source code into an executable graph describing how values are made from other values. From this, I can just run some simple graph algorithms to find what I need.
As a bonus, this allows for some some type checking before execution and to easily paralelize code.
If I made such a language, I imagine it wouldn't allow for reassignment of variables, kinda like SISAL.
Yes, backfeeding has its uses but I don't need it and having acyclical graphs makes my life simpler.
-
Discoverability and gradually increasing user sophistication is nothing new in UX discourse, but I seldom see it connected directly to "real programming". Even in "no-code" there is often a clear separation between the people who glue components together and the people who write new components.
Anyone who has followed me for a few years will have zero surprise to see me bring up #FlowBasedProgramming at this point. 😀 -
@prokoudine That image looks just amazing. I can't imagine the amount of work that goes into something like this.
As someone who doesn't do any visual artwork, what really caught my attention in the "every new feature" clip[0] was the Geometric Node UI. A dataflow network with typed ports and arcs! It would be cool to study just that part and see if it could be extracted for general use in e.g. configuring FBP[1] networks.
[0] invidious.osi.kr/watch?v=JZIFW…
[1] #FlowBasedProgramming -
I discovered some FBP packages I hadn't previously heard of:
- pyflow.readthedocs.io/
- rhei.js colab.coop/blog/how-to-start-f…
- 3-4 Elixir things, dead or alive: elixirforum.com/t/flow-based-p…
#FlowBasedProgramming -
J Paul Morrison, discoverer of #FlowBasedProgramming (FBP) talks about FBP, paradigm shifts, maintainability, mallleability vs brittleness and documentation.
Only 11 minutes and mostly him just straight up sitting in an armchair talking, but quite inspiring.
invidious.snopyta.org/watch?v=…
www.youtube.com/watch?v=up2yhN… -
"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 -
> Reactive Streams is an initiative to provide a standard for asynchronous stream processing with non-blocking back pressure. This encompasses efforts aimed at runtime environments (JVM and JavaScript) as well as network protocols.
Of course I'm immediately curious how this applies to #FlowBasedProgramming . Same thing? A dual? Can FBP be implemented on top?
www.reactive-streams.org/
Heard about this when I discovered that #vertX is still alive.
> Don't like callback-style APIs? Vert.x provides Rx-ified (using RxJava) versions for most of its APIs so you can use those if you prefer.
vertx.io/docs/
There is also a reactivemanifesto.org/ .
@fbp -
Above is, I believe, the first fediverse post about #userland by @hisham_hm .
To help me and others find it again in the future, UserLand is almost, but not entirely, different from #termkit . It's also somewhat vaguely related to #fbp #flowbasedprogramming in a #shell -like context (Hisham does refer to it as an integrated #dataflow environment). It's also not entirely unrelated to #spreadsheet ways of programming.
The original birdsite conversation is also available at nitter.net/pchapuis/status/118… and the repo for the project is at github.com/hishamhm/userland . The project uses #love2d/#löve in #lua . -
My #flowbasedprogramming infection is getting worse. We're looking at how to allow React component siblings to communicate and I'm immediately thinking "I'll need to port some form of FBP to this thing at some point".
-
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.