# Brief History and Evolution — Babel and SWC: JavaScript Transpilation and Build Speed

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

> Trace how transpilation evolved from 6to5 and Babel to the Rust-based SWC and today's faster toolchains.

## Babel's journey since 2014

Babel (originally 6to5) launched to convert ES6 to ES5 so it would run in browsers of the time. Over time it became the standard for JSX, TypeScript and cutting-edge features, and it is still written in JavaScript.

## 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.