<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>React on Gaurav.dev</title><link>/tags/react/</link><description>Recent content in React on Gaurav.dev</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Gaurav. Built with care and clean code.</copyright><lastBuildDate>Wed, 24 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/react/index.xml" rel="self" type="application/rss+xml"/><item><title>Next.js, Remix, and the T3 Stack: Three Different Decisions</title><link>/posts/nextjs-remix-t3-stack/</link><pubDate>Wed, 24 Jun 2026 00:00:00 +0000</pubDate><guid>/posts/nextjs-remix-t3-stack/</guid><description>&lt;p&gt;Next.js, Remix, and the T3 Stack are often compared as if they were equivalent products. They are not. Next.js and Remix provide different models for building React applications, while T3 is an opinionated combination of tools—typically Next.js, TypeScript, tRPC, Prisma, and an authentication solution. Understanding that distinction makes the choice much easier.&lt;/p&gt;&#10;&lt;h2 id="nextjs-a-broad-product-platform"&gt;Next.js: a broad product platform&lt;/h2&gt;&#10;&lt;p&gt;Next.js supports static content, server rendering, server components, route handlers, streaming, and client-side interaction within one ecosystem. It is a strong fit when a product combines marketing pages, authenticated application experiences, search visibility, and a large React component ecosystem.&lt;/p&gt;</description></item></channel></rss>