Derived Data ideas

[NullVoxPopuli]

• intro:
  • problems of not deriving data
    • extra renders (less performant apps)
    • This screenshot from Apple:
      • 
      • our rectangles should not be less performant than video
        • (tho, the stats here could have been caused by the stupid amount of Analytics and Adware folks put on the web)
  • what is "root state"
• use getters to derive data
• use functions to delay data "entanglement"
  • getters are functions
  • what is "entanglement"?
• technique: extract class
  • idea?: compare to custom react hook
• reminders
  • effects / useEffect / etc are bad (usually, not always (tho rarely good))
  • did-update/did-insert bad

Overall goals:

• talk about this generally, applies to all frameworks and reactive systems (except rx.js and other observable focused things which rely on extra renders / wild-west non-performant rendering)
• have examples in React, Signals, Svelte Runes, and Ember (it's all the same)
• have specific sections for each framework calling out specific things to avoid
  • react: useEffect, useLayoutEffect
  • Signals: createEffect
  • Svelte: onMount
  • Ember: did-update, did-insert

[NullVoxPopuli]

Ref:

• https://dev.to/this-is-learning/derivations-in-reactivity-4fo1
• https://frontendmasters.com/blog/vanilla-javascript-reactivity/#signals-pattern-of-solidjs