This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-03
Channels
I guess I wonder if there is anything beyond brevity behind the name? I appreciate brevity, so am in no way suggesting another name.
I appreciate brevity too. There is not much more about it, this is one of the very early choices I made, if I remember correctly the reason was because it's used to "ask" for a value, presumably from a remote location.
Documentation topic - continuous time https://gorgeous-sorbet-a5a2bf.netlify.app/continuous-time.html Please review : • is it too long ? can it be split ? • is it too short ? is there anything missing ? • is jargon well explained ? is there too much of it ?
> Note : {} is called discard and is just a concise way to express (fn [_ x] x). This function is the essence of continuous time, so get used to it !
Loving it!
Trying the examples in the repl is a bit unsatisfying. I want to “inspect” things like x+y, <diamond, and <maybe-input, but I don’t know how to do that. (Maybe I am not supposed to, but anyway.)
Great with all the links to concepts. I’d like more of that. The “diamond test” is referred to as classic, but my google fu fails me. ChatGPT seems to know about it: https://chat.openai.com/share/a35bb7a8-d8d0-44c3-ac08-0bd6e53a5358
continuous time: great section. Gave me a concise explanation to a topic I believe I need to understand. Connecting it to resolution independence (for graphics like for time) helped my understanding a lot. m/signal and m/latest: I didn't understand the difference between these two from reading the sections. I suspect a counter example or two would help - an example where one can be used, but not the other, and why. In general: I'm really glad to see Missionary get more beginner friendly documentation! It's a tool I'm motivated to learn, but I've struggled a bit the brief time I've spent with it. It seems like one of those things that are invaluable once you understand them.
Great read but definitely not for beginners. A lot of advance vocabulary and concepts are used in those paragraphs. Nothing to change, it is just The documentation and it needs to be precise 😉
Here are my remarks:
In "from event stream", code example uses m/observe what's this?
In "from event stream", code example uses ! as function argument. A simple event or e would be more obvious to the "novice" reader.
About the discard shortcut: Examples should be free of shortcuts used by veterans. But of course it is nice to have them in a note at the end of the chapter or the page, if the objective is to infuse idiomatic syntax usage in the community.
Reading "continuous flow composition", I don't understand the motivation for signal , what problem does it solve? latest accepts flows as arguments why wrap them with signal ? Maybe all those questions are related to : What is a publisher?
Once again it is a great read and I learned a lot about continuous flows.