The video is a minute too long for this channel, I hope that's no problem 😊

oh thats a very nice interaction! Its really invites playing with it.

Thanks! This is just the first iteration, I am definitely going to develop it further.

Values can also be json objects, I haven't put that in the video but I do think that this will be helpful

Using expressions as values is brilliant. That's a fantastic insight.

Thanks! 😊 That expression compiler in code flow canvas is really handy.. it's used in a lot of places already and just recently I also implemented a json-mapper node which can have expression in them to generate values for the output json. So it was a no-brainer to add it to these draggable values as well 😀

For Hest, I've been intending to add support for ambiguous values, or constrained values, to help with reversing non-injective functions (see link for examples).

Now, those special values might also make it possible to place any function on a wire. If it's an expression that can be fully evaluated, it works just like what you've shown. But if it can't be fully evaluated, we use amb or constraints (or something) to represent the possible results of the function, and let those flow through the graph.

At this point, the distinction between nodes and values gets pretty blurry. I've also been feeling out the blurry boundary between wires and values. And FP, OO, et al have done a good blurring the boundary between functions and data. So there might be some good realizations that could fall out of a mapping exercise like this:

(the "value" in the top right should be taken to mean "the thing that flows along edges, which might represent data or maybe an expr or something else???")

Suggestion [forgive me, if I've missed noticing that this is already possible]: at 1:44 I would like to de-clutter the diagram by lassoing parts of it and making another diagram ("layer") with the lassoed part. I would like to see the diagram at 1:44 reduced to only 7+-2 boxes, with the details elided to other layers/diagrams, then be allowed to drill down into the sub-diagrams at will if I really want to see more detail.

Ivan Reese the expression in the draggable values are actually evaluated before the value is put on the flow. So only values flow over the edges. Edges can have weights attached to them, but I dont really use that yet (only in a small neural network example)

Paul Tarvydas you're talking about the quicksort flow in the video I assume? That for sure would benefit from sub-flows which you need to drill into. Support for that is still limited in code flow canvas. I can create "compositions" but they dont yet show any values flowing yet and you can't use the timeline slider there yet. So for sure something I want to implement

Ivan Reese if I fill in the mapping exercise then I would place an "x" in every cell except in the function/expr - wire cell

Ah, I'm thinking of doing more than placing an X. I'm thinking: explore that design space in depth :)

Ah 😄 , but aren't we already doing that then in our projects? We could plan a session to talk more about it and share experiences/ideas or have an open discussion about it on one of our FoC meetups?

Yeah, though I think this sort of thing is a good async exercise. I'm going to spend a bit thinking about what could be done with the idea of "let the flowing values be functions"

And then probably come back with some provocations of my own.