Hacker News new | past | comments | ask | show | jobs | submit login

I'm equally curious about flow-based programming. Treating things as filters has worked well for the Unix command line. There's no reason we can't have processes do sort, filter, merge, lookup, and such in well-defined ways and chain them together as needed for many kinds of applications. Although "network" and "port" mean something particular within FBP it doesn't at all mean the processes can't be on different machines and talking via TCP/IP.



There is an interesting equivalence between pure functional programming flow based programming and the actor model.

There is a lot of fancy theory to underpin this equivalence, the essence is that all of them revolve around (side effect free) transformation.


I don't know Erlang and I'm only a couple of months in to learning Elixir in my (limited) free time. Grated, it's not purely functional, but... I've been reflecting on this exact equivalence, as you put it, and am happy to hear that my inclination about the Actor model isn't unfounded.


Ugh, I'm trying to create something like this.

The nodes are fine and easy, but the orchestration / flow implementation is getting me stuck for > 1 month... :(




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: