
Tailwind CSS in 2026: v4 and the New Engine
Picture this: it's a Tuesday morning in early 2025 and your team is staring at a 14-second hot reload on a Next.js 14 app. The Tailwind v3 JIT compiler is choking on a 240,000-line utility scan, your…
Quriostack
7 articles · 9 subcategories

Picture this: it's a Tuesday morning in early 2025 and your team is staring at a 14-second hot reload on a Next.js 14 app. The Tailwind v3 JIT compiler is choking on a 240,000-line utility scan, your…

One of my favourite things to do when I have some down time is to grab a random devkit from my pile of random devkits, and try and write some code that will run on it. I generally try and avoid exist…

The article got pulled into a Slack debate last week between two engineers arguing about whether Tailwind was "real CSS." That conversation is a perfect proxy for the broader industry confusion: ther…

Nuxt 3 scores 89% satisfaction and 73% retention in the State of JS 2024 survey, beating Next.js's 84%, and has become the de facto Vue meta-framework. A friend migrated from hand-rolled Vue 3 + Vite to Nuxt 3 in a weekend, dropping LCP from 6.3s to 1.4s after a Product Hunt traffic spike. The stack pairs Vue 3 auto-imports with file-based routing and Nitro, which compiles to Node, Bun, Deno, Cloudflare Workers, Vercel Edge, or Netlify Edge. Use `runtimeConfig` (not `public`) for secrets and `setResponseHeader` for CDN caching.

A successful admin template rests on four pillars: adaptive layout shell (offcanvas on mobile, persistent sidebar on desktop), scalable navigation with collapse groups and search, density-tuned tables/forms (0.625rem padding), and coherent dark mode via Bootstrap 5.3's CSS variables. The Nimbus template demonstrates sticky sidebar, `/` keyboard shortcut, and theme persistence to avoid flash.

Next.js 15 in 2026: App Router, Server Components, and the New Caching. Last October, Observations included a case where a senior engineer at a 200-person fintech stare at a Vercel dashboard for ten straight minutes. Their marketing page, the one they spent two months rewriting on App Router, was serving

For over a decade, we've relied on window.history to build Single Page Applications (SPAs), and for over a decade, we've complained about it. The reason? It was never really designed for SPAs. To provide a seamless experience, SPAs must mimic standard multi-page navigation by manually tapping into the browser's history to support the back and forward buttons.