The landscape: frameworks, CSS & data

Frameworks

The throughline since 2021 is fine-grained reactivity (signals) and shipping less JS:

• Next.js — dominant React meta-framework (App Router, RSC).
• Astro — content-first, islands; near-zero JS by default.
• React Router v7 — Remix folded back into it; full-stack React.
• TanStack Start — rising, type-safe full-stack.
• Svelte 5 (runes) and SolidJS — signals-based reactivity; Qwik — resumability; Vue 3 / Nuxt.
• Tooling: Vite won; Create React App is dead.

CSS caught up

A lot of what needed a library in 2021 is now native CSS — so you often reach for Tailwind + plain CSS instead of CSS-in-JS:

/* native nesting, container queries, :has(), color-mix, oklch */
.card {
  &:has(img) { padding-block: 1rem; }
  @container (min-width: 30rem) { display: grid; }
  background: color-mix(in oklch, var(--brand) 12%, white);
}

Plus the View Transitions API for animated route/state changes, subgrid, cascade layers, and @property. Component-wise, headless (Radix) + copy-own (shadcn/ui) replaced heavy component kits.

Databases & ORMs

Past Postgres / MySQL / Mongo:

• Postgres is the default again — with pgvector (RAG), PostGIS; serverless via Neon / Supabase.
• SQLite at the edge — Turso / libSQL, Cloudflare D1, local-first.
• Vector DBs for AI — Pinecone, Qdrant, Weaviate (or pgvector).
• OLAP — DuckDB, ClickHouse. ORMs — Drizzle (SQL-first, rising) vs Prisma.

The challenge models the signals idea underneath Svelte/Solid/Vue: a value with dependents that recompute only when their source changes. Run it.

Run it. A derived value recomputes only when a signal it depends on actually changes — fine-grained reactivity in miniature.

Loading editor…

That's the catch-up: server-first React, a compiler that memoizes for you, state split into server and client, and a platform (frameworks, CSS, data) that does more so your code ships less.