| title | Why Respo | ||
|---|---|---|---|
| scope | module | ||
| kind | guide | ||
| category | intro | ||
| aliases |
|
||
| entry_for |
|
📚 Documentation Index
- ← Back to README
- Beginner Guide
- 🤖 Respo-Agent Guide - For LLM development
- API Reference
- All Guides: Base Components | Virtual DOM | Component States | Styles | Events?
There are quite some alternatives actually: Reagent, Om, React.js , Deku, or Rum. I think Om is too complicated for me.
The different part of Respo is, it's built in Calcit-js with persistent data structure from scratch. It can be too simple for real world apps that requires lots of side effects, but it is fine to build medium size apps and do experiments about MVC. Respo is designed carefully to maintain global store and global states, as a result hot code swapping is more predictable.
For short, it's simpler, meanwhile purer.