> I hope this makes it clear, or at least strongly hints, that this is not the usual low-code/no-code trick of achieving compact code by creating super-specialised components and mechanisms that work well for a specific application, but immediately break down when pushed beyond the demo.
That's... not clear at all to me. This seems like the kind of code that is fun to write, annoying to read, infuriating to debug.
The dataflow part where text flows into an S3 file is interesting, but it feels like as you get into corner cases that need more complex transformations with more potential bugs, the "just bind this value to its destination" syntax would quickly become cumbersome, and you'd want something closer to RxJS.
That's... not clear at all to me. This seems like the kind of code that is fun to write, annoying to read, infuriating to debug.
The dataflow part where text flows into an S3 file is interesting, but it feels like as you get into corner cases that need more complex transformations with more potential bugs, the "just bind this value to its destination" syntax would quickly become cumbersome, and you'd want something closer to RxJS.