Earlier quoted context omitted.
Why would it be good when a node is data, since the data is always changing and the function would stay the same?
the Scoped Propagator model is based on two key insights: 1. by representing computation as mappings between nodes along edges, you do not need to know at design-time what node types exist. 2. by scoping the propagation to events, you can augment nodes with interactive behaviour suitable for the environment in which SPs have been embedded. It's pretty specific to UI similar to the examples, but in terms of these big…
Scoped Propagators
21–30 of 32 posts
Re: Scoped Propagators
#22Earlier quoted context omitted.
All but two of the videos are broken for me on both Chrome and Firefox. I would love to see the rest! I encourage people to read the original Propagator Networks paper by Alexey Radul (advisor: Prof. Gerald Sussman of SICP) referenced in the Prior Work section. It's full of fascinating ideas. https://dspace.mit.edu/handle/1721.1/54635
Would love to know which videos are broken and any other details so I can try and fix that!
Re: Scoped Propagators
#23Earlier quoted context omitted.
I only glanced at the article, but it also reminds me of Dataflow programming, incrementally updated materialized views, etc. (all the same concept at the end of the day, and yes, very similar to observables)
It remind you of dataflow programming because it's literally the same thing.
Basically, the "scopes" become constraints, and they use a hierarchical constraint solver to propagate state changes to the GUI elements, real-time, using a declarative dataflow programming model.
Re: Scoped Propagators
#24Re: Scoped Propagators
#25Re: Scoped Propagators
#26One of the first thing that comes to mind was is about Smalltalk, and the idea that it is about the messages and not the objects.
The next thing to come in mind is about how this allows for composition of interactions. I think it can enable highly local customization that can still receive software updates from upstream. I am thinking about how one of the problems with extensible specifications (such as XMPP) eventually lead to an ecosystem where feature updates cannot propogate easily; and we might see something like that in the Fediverse
Re: Scoped Propagators
#27Re: Scoped Propagators
#28Re: Scoped Propagators
#29Some of the videos are broken for me (using Firefox). Otherwise looks pretty neat. Compared to FRP it is perhaps a bit more declarative in the definition of scopes, but otherwise seems equivalent. I'm interested in more details on this. I'm also a bit confused by > This model has not yet been formalised, and while the propagators themselves can be simply expressed as a function ... I have not yet found an appropriate…
> Compared to FRP it is perhaps a bit more declarative in the definition of scopes, but otherwise seems equivalent. FRP systems are typically limited to acyclic graphs. The system in this article allows for cycles.
Re: Scoped Propagators
#30Earlier quoted context omitted.
> Compared to FRP it is perhaps a bit more declarative in the definition of scopes, but otherwise seems equivalent. FRP systems are typically limited to acyclic graphs. The system in this article allows for cycles.
Every FRP system I've used allows cycles.