Explanation
Where This Model Fits
Understand the design decisions, alternatives, and limits.
TSXLight is not presented as a replacement for modern client React. It is an experiment in a different ownership model. The design fits best when the server is already the trusted authority, when the UI is controlled, and when a full browser-side state machine would be more liability than benefit: internal tools, desktop shells, demos, admin consoles, or teaching environments.
The same ownership model is a poor fit for latency-sensitive drawing tools, offline-first applications, public high-scale frontends, or interfaces that need rich browser-local interaction between server turns. Every meaningful event has to cross the socket boundary, so network latency and connection lifecycle become part of the rendering contract.
- Server ownership simplifies authority and persistence for controlled shells.
- Callback serialization makes event identity explicit but adds protocol and lifecycle complexity.
- Per-user renderers prevent accidental shared state but require careful cleanup for duplicate connections.
- Full-shell rerendering is understandable, but it lacks the efficiency of browser-side reconciliation.