# Brief History and Evolution — Babel & SWC

Source: https://www.geekswithgeeks.com/en/babel-swc/bs-history

> From ES5 to modern tooling: how transpilation evolved.

## Babel's journey since 2014

Babel (originally 6to5) launched to convert ES6 to ES5 for IE10 users. Over time, it became the standard for JSX, TypeScript, and cutting-edge features. Still JavaScript-based.

## The SWC revolution (2018+)

SWC emerged as a Rust rewrite of Babel, offering massive performance gains. It's now the default in Vercel's Next.js, tightly integrated with modern frameworks, and the future of transpilation.

## Coexistence, not replacement

Babel is still widely used and mature. SWC is faster but younger. Both are thriving; many projects run SWC but fall back to Babel plugins for edge cases.

## Current ecosystem maturity

Babel has 1000+ community plugins. SWC has fewer but covers 95% of use cases. For most projects, SWC's built-in features are sufficient.