<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Halfnelson on React Templates &amp; Themes</title><link>https://www.reacttemplates.dev/author/halfnelson/</link><description>Recent content in Halfnelson on React Templates &amp; Themes</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://www.reacttemplates.dev/author/halfnelson/index.xml" rel="self" type="application/rss+xml"/><item><title>Svelte It Will Scale</title><link>https://www.reacttemplates.dev/theme/halfnelson-svelte-it-will-scale/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.reacttemplates.dev/theme/halfnelson-svelte-it-will-scale/</guid><description>&lt;h2 id="overview">Overview:&lt;/h2>
&lt;p>In this article, the author discusses the concept of an inflection point in Svelte and React bundle sizes and determines the size at which the advantage of using a compiler over a runtime diminishes. The author analyzes the relationship between component source code size and bundle size for both Svelte and React and finds that the inflection point for Svelte is around 120KB of component source. They also note that in practice, as long as code-splitting is used, it is unlikely to hit the inflection point on any given page of an app. The author concludes that Svelte projects tend to be lean and can scale effectively.&lt;/p></description></item></channel></rss>