I'm the creator of Primate, so take the title with the appropriate grain of salt. By "great web framework" I mean a tool that owns the whole stack—routing, rendering, data, validation, sessions, deployment targets, runtime support—designed to fit together seamlessly.

In the JavaScript world, composition dominates: pick a server framework, a database client, a validation library, a frontend, a build tool, and glue them together. Each piece may be excellent alone, but nobody owns the seams. Meta‑frameworks enforce cohesion but lock you into a single stack, and runtime fragmentation (Node, Deno, Bun) ties frameworks to specific runtimes, even when they only support Node APIs.

Primate removes that coupling. It provides one application model and lets you choose referencias route‑by‑route: React where it fits, Svelte elsewhere, TypeScript, Go, Ruby, or Python for the backend, and run on Node today and Deno tomorrow. The framework still handles validation, databases, sessions, i18n, routing, and rendering, but it does not lock you into any particular frontend, backend language, or runtime.

A small demo shows the same routing model with different frontends; the backend route logic stays unchanged. The current limitation is that layouts cannot be shared across frontends, though web components may enable that later.