[HN Gopher] Developing a reactivity system with Lamport clocks a... ___________________________________________________________________ Developing a reactivity system with Lamport clocks and incremental computation Author : pcr910303 Score : 13 points Date : 2020-09-26 12:04 UTC (10 hours ago) (HTM) web link (v5.chriskrycho.com) (TXT) w3m dump (v5.chriskrycho.com) | knuthsat wrote: | This looks exactly like MobX | chriskrycho wrote: | There are definitely similarities! A key difference is that you | can actually implement MobX _in terms of autotracking_. | Autotracking is a lower-level primitive that you can use for | all sorts of higher-level systems. | sudders wrote: | This really is brilliant in its simplicity. | | Not having to maintain complex data structures to keep track of | property dependencies as opposed to using light weight integer | comparison to track changes. I can imagine @tracked being many | times faster than @computed | chriskrycho wrote: | It's both faster out of the box _and_ uses much, much less | memory--which _also_ makes it faster. As I note in the summary | at the bottom of the post, because it provides no value-level | caching out of the box, it does a great deal less work than the | `@computed` system, and is about as cheap as it can be. But | that also means you have the flexibility to layer in value- | level caching when _that's_ the right tradeoff: something which | is notoriously difficult to do (especially to do _correctly_ ) | in a `@computed`-style system. ___________________________________________________________________ (page generated 2020-09-26 23:00 UTC)