Benchmark 2025: TypeScript vs Competitors — Who Wins in Speed?
In 2025, the TypeScript ecosystem continues to strengthen: the language is actively used not only for frontend, but also for backend, microservices, and even CLI utilities. However, how fast is it compared to traditional "heavyweights"? We analyzed the latest benchmarks published in the first quarter of 2025 and prepared a brief overview.
Testing Methodology
Tests were conducted on a standardized set of tasks (loops, string manipulation, arrays, JSON parsing, floating-point calculations). The following languages and runtimes participated:
- TypeScript 5.6 (Node.js 22, Bun 1.2)
- Rust (1.82, compilation — release)
- Go (1.23)
- Python 3.13
- Java 21 (GraalVM)
Results: Execution Speed
The leader in raw performance remains Rust — it is on average 3–5 times faster than TypeScript on computations. However, TypeScript on Bun shows unexpectedly high results:
- TypeScript (Bun) — 1.0x (baseline for comparison)
- Go — 0.8x of TypeScript (slightly slower on JSON operations)
- Java (GraalVM) — 0.9x (almost parity, but higher memory consumption)
- Python — 0.25x (expectedly slower)
Memory Consumption and Startup
Here, TypeScript (Node.js) lags behind Rust and Go — 40–60 MB vs 5–10 MB. However, Bun has narrowed the gap to 20–25 MB. Cold startup time:
- Rust: 1–3 ms
- Go: 2–5 ms
- TypeScript (Bun): 15–25 ms
- TypeScript (Node): 50–80 ms
- Java: 150–300 ms
Conclusions for Developers in 2025
TypeScript hasn't become faster than Rust or Go, but it has significantly improved its metrics thanks to Bun and new V8 optimizations. For most web applications, APIs, and scripts, TypeScript remains a reasonable choice: development speed and ecosystem outweigh the 10–20% performance loss.
If you need maximum performance for every millisecond — go with Rust or Go. If development speed and type safety are important — TypeScript in 2025 won't let you down.