Thank you both for the answers! > the thing that would have helped me most in avoiding some of the missteps might have been a richer test interpreter, where I could have "mocked" a network This is a really intriguing…
No offense taken - re-reading what I wrote, you make a fair point. The wiki page luckysid linked calls this out: > Confusingly, the term refers to overall invisibility of the component, it does not refer to visibility…
I had a few questions: 1. The posts mention Spark, but were you (the Unison team) also inspired by dataflow / stream processing engines (e.g. Flink, Beam, Timely Dataflow etc.) or any other technologies? 2. Relatedly,…
I think there were a lot of great ideas presented in these small examples. 1. Explicitly marking non-local _data_ vs. in-memory. A very cool idea -- languages and libraries I've used all seem to try to make this…
Thank you both for the answers! > the thing that would have helped me most in avoiding some of the missteps might have been a richer test interpreter, where I could have "mocked" a network This is a really intriguing…
No offense taken - re-reading what I wrote, you make a fair point. The wiki page luckysid linked calls this out: > Confusingly, the term refers to overall invisibility of the component, it does not refer to visibility…
I had a few questions: 1. The posts mention Spark, but were you (the Unison team) also inspired by dataflow / stream processing engines (e.g. Flink, Beam, Timely Dataflow etc.) or any other technologies? 2. Relatedly,…
I think there were a lot of great ideas presented in these small examples. 1. Explicitly marking non-local _data_ vs. in-memory. A very cool idea -- languages and libraries I've used all seem to try to make this…