Reactivity lives in the framework's foundation, not bolted on top.Dependency arrays, manual subscriptions, manual cache invalidation, effect cleanup — none of it exists here. Not made easier, made unnecessary.Get StartedTry PlaygroundWhy $molview.tree$my_hello$mol_view guest \stranger sub /<= Name $mol_string value?<=> name?\mol hint @ \Type a name<= Greeting $mol_paragraph title <= greeting \view.tsclass $my_helloextends$.$my_hello{greeting(){return `Hello, ${ this.name() || this.guest() }!`}}view.css.tsnamespace ${$mol_style_define($my_hello,{gap:$mol_gap.block,flex:{direction:'column'},Greeting:{font:{size:'2rem',weight:600},},})}→liveHello, mol!Three files: the markup, the logic and the styles.Try this exampleMinimalisticAn incrementally adoptable ecosystem that scales between a single component and a full-stack local-first app.OptimalBuild UIs as trees of components. Reactivity is automatic, side-effects are explicit.LazyFull rendering virtualization — components outside the viewport simply do not exist.Structure