Tag: performance

40 Languages, 400KB Bundle — Why I Refuse to Ship Translations in JavaScript

How dynamic translation loading with client-side caching serves 40 locales without bloating the SPA bundle, keeping the React app under 400KB while supporting instant language switching.

480 Pages, 40 Locales, Zero Frameworks — How I Beat Next.js at International SEO

How we bake hreflang tags, Schema.org structured data, and locale-specific Open Graph metadata into 480 static HTML pages at build time — without any client-side i18n framework or SSR.

I Killed the Loading Spinner — Without Next.js, Without SSR, Without Any Framework

How a 6-line data injection pattern eliminates the loading spinner from React SPAs by injecting server data into HTML and pre-populating React Query's cache before the first render.

I Deleted a 200MB Rust Binary From My Docker Image. My Deploys Have Never Been the Same.

How migrating from Prisma 5's Rust query engine to Prisma 7's pure-JavaScript driver adapter cut our Docker image by 42%, slashed cold starts by 68%, and gave us back control of our connection pool.

Your Users Download 1.5MB of JavaScript to See a Landing Page. We Fixed It With an If Statement.

How we split a React SPA into public (400KB), auth (150KB), and private (1.5MB) bundles — selected server-side by URL path, built with Bun, zero framework required.

We Built a 340-Line Static Site Generator That Made Next.js Irrelevant. It Renders 480 Pages in 650ms.

How mentoring.oakoliver.com generates 40 locales × 12 routes at server startup using React 19, hydrates with React Query, and why we'll never go back to a framework for this.

We Replaced Node.js With Bun Across Every Production Service. Here's What Nobody Tells You.

The real story of migrating three production services from Node.js to Bun on a single VPS — cold starts, memory savings, deleted dependencies, and every gotcha that bit us.