React
- 500KB+ bundle for a simple app
- Complex state management
- Build tooling overhead
- Client does all the work
htm/a
4KB
Server-side reactivity. Zero dependencies.
The Problem with Modern Web
htm/a
- 4KB total bundle size
- Server manages all state
- Zero build step required
- Type-safe Rust backend
Size Comparison
The EASL Pattern
A linear, unidirectional architecture that keeps complexity where it belongs: on the server.
Event
User action on client
Actor
Business logic on server
Stream
HTML updates to client
Lined
Linear, unidirectional
See It in Action
The Actor
<htma-actor name="Counter"> {% let value: i32 = 0 %} <htma-template> <div class="counter"> <h1>{{ value }}</h1> <button htma-action="decrement">-</button> <button htma-action="increment">+</button> </div> </htma-template> {% action increment sync %} {% value += 1 %} {% endaction %} {% action decrement sync %} {% value -= 1 %} {% endaction %} </htma-actor>
The Result
...
Speed Test
htm/a
0
Features
Zero Client Dependencies
No npm, no node_modules, no bundler. Just one script tag.
Type-safe Rust
Catch errors at compile time. No runtime surprises.
WebSocket & SSE
Real-time bidirectional or unidirectional streaming. Your choice.
Actor Model
Isolated state, message passing, no shared mutable state.
HTMX Superset
Start simple with HTTP. Upgrade to WebSocket when ready.
4KB Bundle
35x smaller than React. Fast on any connection.
Works with minline.js
Combine with minline.js for templating, i18n and preferences.
Get Started
Three steps. That's all it takes.
Create a new project
cargo new my-app
cd my-app
cargo add htma
Include the client
<script src="htma.js"></script>
Connect to your Actor
<htma-endpoint url="/ws"> <htma-actor name="Counter"></htma-actor> </htma-endpoint>