· product · showcase
Not demos — shipped products. Same component model, two compilers. Proof that compiler-first scales beyond todo apps.
Ops dashboard for a deployment platform. Streams logs, parallel revalidation, offline-aware routing.
Vesk · useFetch · Tailwind
→ 1,200-row live table — O(1) per-cell, 0 jank
Offline-first field notes with camera, GPS, and sync. One .vsk codebase, Kotlin on device.
Vesk Native · Kotlin · Compose
→ Works offline by default — same offline.vsk as web
Docs site and native help share the same library. Design tokens and Markdown pipeline are one.
One codebase
→ No drift — web + help ship from same commit
| Metric (median) | Vesk | Next.js 15 + React | SvelteKit |
|---|---|---|---|
| Home — JS shipped (gzip) | ~22 kB (static) / 48 kB (dashboard) | ~95-140 kB | ~28-45 kB |
| Hydration cost (main thread) | claim walk, static skipped | hydrateRoot full replay | hydration + runtime |
| List update 1k rows | O(1) one text node | O(n) VDOM + diff | O(1) — Svelte fine |
| Build → .vesk (cold) | ~1.8 s (CI, 24 pages) | ~4-6 s | ~2-3 s |
* Numbers from showcase builds on same CI (4 vCPU, Node 20). Your app will differ — win is architectural, not a micro-benchmark.