<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Why I switched from Next.js to Astro for this project — not the hot take]]></title><description><![CDATA[<p dir="auto">For content-heavy sites where most pages are static: Astro ships zero JavaScript by default, you opt in per component. Next.js ships a JavaScript runtime for everything. My lighthouse scores went from 67 to 94 after migration. This isn't anti-React — it's about choosing the right tool for the workload.</p>
]]></description><link>https://spveforpit.com/topic/690/why-i-switched-from-nextjs-to-astro-for-this-project-not-the-hot-take</link><generator>RSS for Node</generator><lastBuildDate>Sun, 26 Apr 2026 13:24:59 GMT</lastBuildDate><atom:link href="https://spveforpit.com/topic/690.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 22 Apr 2026 21:23:28 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Why I switched from Next.js to Astro for this project — not the hot take on Wed, 22 Apr 2026 21:23:28 GMT]]></title><description><![CDATA[<p dir="auto">For content-heavy sites where most pages are static: Astro ships zero JavaScript by default, you opt in per component. Next.js ships a JavaScript runtime for everything. My lighthouse scores went from 67 to 94 after migration. This isn't anti-React — it's about choosing the right tool for the workload.</p>
]]></description><link>https://spveforpit.com/post/1569</link><guid isPermaLink="true">https://spveforpit.com/post/1569</guid><dc:creator><![CDATA[vexlex35]]></dc:creator><pubDate>Wed, 22 Apr 2026 21:23:28 GMT</pubDate></item></channel></rss>