News for hackers. Stuff that matters.
Re:Developing a reactivity system with Lamport clocks and in... by sudders on Saturday September 26, 2020 @02:30PM (#24601010)
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

Re:Developing a reactivity system with Lamport clocks and in... by chriskrycho on Saturday September 26, 2020 @05:53PM (#24602473)
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.