zlacker

[return to "Understanding Kafka with Factorio (2019)"]
1. haswel+0i1[view] [source] 2023-07-13 20:06:50
>>pul+(OP)
I recently started playing Factorio, and I kept thinking that this is what "low code" integration/automation tools should look like. Developer tooling with extremely clear visuals, obvious dataflow, endless combinations into which the rigidly defined components can be assembled to do exactly what they do.

As opposed to so many takes on "flow based" programming, which present some imperfect nodal representation of the program, but rarely can the user make sense of what's going on by seeing stuff moving around as the thing executes.

And by the way, be sure you're ready to sink some time in if you're curious about this game...it's just too good, and I've had to consciously reduce the time I'm spending, because I could just keep optimizing...building...expanding...optimizing...it's built in the shape of the reward center of my brain.

◧◩
2. samsqu+xN2[view] [source] 2023-07-14 08:32:33
>>haswel+0i1
I am interested in this topic, so thank you for mentioning it.

I haven't played Factorio but this article GIFs helped me understand it, at least from a high level simplistic perspective!

I think most of programming is just logistics: moving data from one place to another, picking and choosing what fields to use for a given purpose and then calling a function with those selected parameters or talking to another system.

I am working on a number of experiments in this area. I'm working on a programming environment which is unlike programming languages where you specify instructions and the state is implied but you work directly with state and instructions are implied.

The problem with nodal editors is that they're not very information dense.

[go to top]