Comparison

# Feature matrix

# When to choose Nix.js Kit

# Choose Nix.js Kit if:

• You want Next.js conventions (file-based routing, layouts, actions, API routes) without the React tax
• You want Astro-style islands with fine-grained signals instead of full hydration
• You want a single framework that handles both content sites and interactive apps
• You value zero client dependencies and a ~14KB runtime
• You want TypeScript 7 with the native Go compiler
• You want CSRF protection and progressive enhancement built-in

# Choose Astro if:

• You need the largest ecosystem of integrations (MDX, React, Vue, Svelte components)
• You need more adapters (Cloudflare, Deno, etc.)
• You want mature streaming support
• You're building a content-heavy site with minimal interactivity

# Choose Next.js if:

• You're already invested in the React ecosystem
• You need React Server Components
• You want the largest community and commercial support
• You need advanced features like next/font, next/script, Turbopack
• You're building a highly interactive app where React's ecosystem matters

# Philosophy differences

# Nix.js Kit

• Signal-based reactivity — no virtual DOM, no diffing
• Tagged template literals — no JSX, no compiler step
• Zero dependencies — optional peer deps only for content/images
• Progressive enhancement — actions work without JavaScript

# Astro

• Multi-framework — use React, Vue, Svelte, or plain HTML
• Islands by default — zero JS unless you opt in
• Content-first — built for blogs, docs, marketing sites

# Next.js

• React-first — everything is a React component
• RSC — server components reduce client bundle
• Full-stack — API routes, actions, database, caching all built-in
• Vercel-optimized — best DX on Vercel's platform