3 ms·
It looks like you put a lot of thought into this! Connective allows users to create graphs between sources and sinks flexibly (i.e., not only source to sink al
by maxbendick 7y ago
It looks like you put a lot of thought into this!
Connective allows users to create graphs between sources and sinks flexibly (i.e., not only source to sink ala typical RxJS), without needing to worry about multicasting.
Is this a fair way to describe this library's benefit?
- lorean_victor 7y agothe first benefit, yes (although I would say it is already two, the "graph" and the "flexible connection"). the second one being offering abstractions for re-use of partial graphs. and it is notable that though CONNECTIVE takes away the worry of multi-casting in (hopefully) a lot of the cases, it is actually pretty conservative on that front and will in a number of cases default to not-multicasting, which might mean that you can get some unexpected behaviors if you are completely unaware of the concept. the plan is to expand the situations that it will make a good default decision for you on that front overtime based on how it is actually used. EDIT: also thanks, yes as I mentioned somewhere else I actually started doing this for a super-efficient frontend framework (that effort epically failed), so I ended up being extra careful about a lot design choices (and to be fair, carefully delegating a lot of such choices to RxJS as it is a really brilliantly designed library itself).