← Back to home
Comparison · DevOps

Bun vs Argo CD

Side-by-side trajectory, velocity, and editorial themes.

B
Bun
DEVOPS
3.8

Bun is rewriting its core from Zig to Rust while shipping built-in APIs at a monthly clip.

◆ Current state

Bun ships a substantial point release roughly monthly, each widening Node.js compatibility and folding more capability into the runtime itself — image processing, Markdown parsing, cron, archives, a headless WebView, HTTP/2 and HTTP/3 clients. Performance work is constant, with double-digit speedups landing release over release. In July the team disclosed it is rewriting Bun's implementation from Zig to Rust.

◆ Where it's heading

Two arcs run in parallel: keep absorbing what developers reach for third-party packages to do, so the runtime is batteries-included, and re-lay the foundation in Rust for a larger contributor pool and easier maintenance. The near-term feature cadence has not slowed, which suggests the rewrite is incremental rather than a hard fork.

◆ Prediction

Expect continued monthly 1.3.x releases centered on Node compatibility and built-in APIs, with the Rust migration surfaced through engineering write-ups before it changes anything user-facing.

A
Argo CD
DEVOPS
6.3

Argo CD's 3.5 line is in release-candidate hardening after a feature-heavy rc1 (Helm 4, supply-chain, Gateway API).

◆ Current state

Argo CD shipped 3.4.0 to GA and has moved the 3.5 line into release candidates. The 3.5.0-rc1 carried a large feature set: Helm 3-to-4 migration, opt-in source-integrity verification for the hydrator, Gateway API support in the network view, mTLS in the repo-server, server-operation impersonation, and ApplicationSet UI work, while rc2 is bug-fix stabilization. The project keeps a strong supply-chain posture with cosign-signed images and SLSA Level 3 provenance.

◆ Where it's heading

Argo CD is converging 3.5 toward GA, so expect further rc bug-fix rounds until it stabilizes. The 3.5 theme blends supply-chain security (source integrity, provenance, mTLS), ecosystem currency (Helm 4, Gateway API), and ApplicationSet and UI maturation. After GA, the rolling stable tag advances and the 3.4 line drops to maintenance cherry-picks.

◆ Prediction

Expect one or more further 3.5.0 release candidates with bug-fix cherry-picks, then a 3.5.0 GA that moves the rolling stable tag forward.

See more alternatives to Bun
See more alternatives to Argo CD