tmk241
8 lines
1.2 KiB
Plaintext
8 lines
1.2 KiB
Plaintext
ID PROBLEM FOR OUTCOME
|
|
server/001 Browser frameworks duplicate authoritative application state and policy Rust teams building ordinary server-owned web applications Keep state, authorization, validation, and recovery on the server
|
|
resource/001 Copied selectors and protocol identifiers drift away from rendered templates Template and handler authors Use generated typed resources and actions for every interaction boundary
|
|
protocol/001 Ad hoc browser commands create ambiguous ordering and compatibility Framework adapters and browser runtimes Apply one deterministic ordered effect protocol within an owned root
|
|
web/001 Framework abstractions often replace native web semantics unnecessarily People using Hemx applications Retain semantic HTML, accessibility, URLs, forms, and browser fallback
|
|
portable/001 Host-only parsing dependencies prevent portable server-side rendering Rust applications targeting Wasm and constrained servers Render through normal Hemx APIs without host parser dependencies
|
|
scope/001 Universal extension systems turn a small interaction layer into a client framework Maintainers and application authors Compose ordinary behavior from a small kernel, direct adapters, and explicit islands
|