RFC: Evolving State Management (Svelte-style stores, Signals, & Client-side Generation)

[reecelikesramen]

As PyWire grows, we want to ensure our state management remains intuitive but becomes more performant—especially in reducing unnecessary server roundtrips for purely cosmetic or highly interactive client-side state.

Key Concepts to Explore:

• Svelte-Style Stores & Signals: Can we introduce a more robust context or store system (akin to Svelte Stores or Signals) to avoid prop drilling and handle multi-component shared state clearly?
• Client-Side State Generation & Sync: Currently, PyWire leans heavily on server roundtrips for wire updates. We should explore a hybrid approach where certain state is explicitly marked for client-side evaluation (using a signals paradigm) to reduce server load and latency.
• Prototyping Client-Side JSX/JS Generation: Could the compiler generate pure JS reactivity for specific templates instead of always relying on morphdom diffs from the server?

Questions for the community:
How do you currently handle complex client-side interactions? Would a built-in signals library or a pywire.store namespace make sense, and what syntax feels most "Pythonic"?