Skip to main content

Reactivity and signals: demystifying frontend magic

How does a frontend know which code to run after state changes? This talk answers the question with ui = fn(state), an Excel example, and a small reactive system built with alien-signals.

It introduces dependency graphs and doubly linked lists, then explores subscribers, computed values, effects, propagation strategies, and several unresolved problems such as glitches, cycles, mutable state, and changing dependency graphs. The last examples show how these mechanisms map to Vue.

Enjoyed "Reactivity and signals: demystifying frontend magic"?

Follow me

Estéban Soubiran

Software engineer, conference speaker, and open source enthusiast.

Explore more talks

  1. Event: Paris TypeScript (opens in a new tab)ParisDate:

    In JavaScript, there's a package for everything... and often for nothing.

  2. Event: MiXiT (opens in a new tab)LyonDate:

    Reactivity and signals: demystifying frontend magic

  3. Event: Asynconf (opens in a new tab)ParisDate:

    Reactivity and signals: demystifying frontend magic

What do you think?

Discussions

Loading discussions...

Add a comment

Checking your session...