7 Principles of Rich Web Applications
Guillermo Rauch · Reviewed .
What the source supports
The essay argues for useful pre-rendered content, immediate feedback, controlled data exchange, preserved history, and live updates. It explicitly distinguishes actions suitable for optimistic feedback from sensitive outcomes such as payments.
Thorbis translation
A payment may acknowledge submission immediately while remaining pending until confirmed. A list should preserve its place when a person opens a record and returns. Recovery must account for network failure.
What we are not adopting
No blanket optimistic success, overwriting active drafts with pushed data, or transplanting historical SPDY and server-push advice into the current stack.
Existing owners and review exercises
These are Thorbis applications and review exercises, not replacements for DESIGN.md, COMPONENTS.md, or the owning skill. Linear remains the operational baseline. External advice that conflicts with the constitution stays out.