React vs Svelte

Frontend frameworks.

Overview

React and Svelte are two leading frontend frameworks with very different philosophies. React centres on a virtual DOM with runtime reconciliation, backed by the largest frontend ecosystem on earth. Svelte centres on a compile-time approach that produces small JS bundles with no runtime framework. The right answer depends on whether ecosystem breadth or runtime efficiency dominates the team's constraints.

• React: ecosystem maturity. Largest frontend ecosystem, every UI library, every job description, decade of production knowledge. Default for organisations that need to hire from a deep talent pool.
• Svelte: compile-time approach. No runtime framework, small bundles, simpler reactivity model. Default for performance-sensitive apps and teams that prefer less framework overhead.
• Operational fit per team. Existing component libraries and team React expertise bias toward React; greenfield apps with performance constraints bias toward Svelte.
• Per-app choice. Different apps may pick differently. Document the rationale per app rather than enforcing one framework org-wide.

The approach

Workload-driven choice, per-team operational fit considered, documented rationale per app. The discipline is making the framework choice once with a written reason rather than mixing both frameworks across apps that share components.

• Workload-driven. Framework per app. Reality drives the answer.
• React for ecosystem-dependent apps. Apps that need third-party UI libraries, design systems, or large hiring pools.
• Svelte for performance-sensitive greenfield apps. Small bundles, fast first paint, simpler reactivity. Default when performance constraints drive the choice.
• Operational fit plus documented rationale. Team workflow considered; per-app rationale captured. Future migrations have a paper trail.

Why this compounds

The right framework choice compounds across years. Component libraries and design systems align with the framework; team expertise deepens; cross-app patterns get reused. By year two the framework choice is automatic per app and the design system is cohesive across the surface area.

• Better operational fit. Framework matches team. Velocity stays high.
• Workload-driven decisions. Replaces tribal preference with documented rationale. Quality of choice improves.
• Better engineering velocity. Right framework means components compose cleanly. New features ship faster.
• Year-one investment, year-two habit. First framework choice is the investment; subsequent apps inherit the patterns.