In the context of decentralized data, social, and revision control, immutability+references+history have nice properties.
-
-
-
Works for Git, Etherium. Social networks are 99% write-once, 1% revise-past-stuff.
End of conversation
New conversation -
-
-
I'm experimenting with distributed data in a social/metaverse context, which you'd want to run both native and in-browser.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Picture social graphs and timelines where everyone's content references everyone else's arbitrarily. Like the one right here!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This probably would best be a data later on top of IPFS, that's just not the easiest way to prototype it.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Yes, and practical if a language/framework encourages mostly-immutable data and mostly-pure functions.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Example: Surfacing a 60TB GitHub repository as lazy traversable data structures. You'd better not initiate loading it all!
-
Observables are lazy, like async iterables. Work only happens on subscribe, also cancelable. Very fast with rxjs5
@BenLesh
End of conversation
New conversation -
-
-
wouldn't that just be lambdas or lambdas that returned promises?
-
Could be, but that doesn't necessarily capture the chaining and recalculation relationships between lazy and async computation.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.