Vite 8.0 Is Out

Original Article ↗ Hacker News Discussion ↗

Performance & Real‑World Impact

  • Multiple reports of dramatic build speedups upgrading to Vite 8, often 4–8x faster; examples include 4m→30s, 12m→2m, 2m30→35s, 10s→1s.
  • Gains attributed mainly to the Rust-based Rolldown bundler and Oxc tooling.
  • Some express disbelief that JS apps can have 10–12 minute builds at all, but others note million‑LOC apps, slow CI machines, and poor build optimization.
  • Faster builds are framed as not just convenience but critical for developer and AI-agent feedback loops.

Oxc, Rolldown, and TypeScript Features

  • Oxc supports various TS runtime features (parameter properties, enums) and TS “experimental decorators”.
  • It currently does not downlevel TC39-standard decorators and lacks const enum support, unlike esbuild.
  • TC39 decorator emit recently landed in a related project, with hope it surfaces in Vite soon.
  • Questions about using Rolldown as a Rust crate reflect interest in a fully Rust toolchain instead of SWC/Deno.

Next.js vs Vite and Alternatives

  • Strong sentiment that Next.js has become bloated, confusing, and tightly coupled to Vercel’s hosting model.
  • Complaints about long builds, caching complexity, security issues, RSC confusion, and poor DX for static export and typed API routes.
  • Several suggest migrating to Vite + TanStack Router/Start, Astro, or simpler SPA setups for static or hybrid apps.
  • Some note that major enterprise integrations and official React docs emphasizing frameworks have reinforced Next’s dominance despite better options.

Rust, Node, and Tooling Direction

  • Many celebrate Rust rewrites for tooling (Vite/Rolldown/Oxc) as proof Node is too slow for modern build systems.
  • Debate over using Rust (or other compiled languages) for backends: some praise performance and robustness; others call Rust overkill or too complex for most teams.
  • Comparisons with Go, Java, .NET, and Bun; concern that requiring plugins or app logic in Rust would hurt ecosystems.

Build Tools, Config, and Maintainability

  • Vite is contrasted favorably with historical webpack/CRA complexity; LLMs are being used to convert old configs to simple Vite setups.
  • Some prefer using esbuild directly for long-term stability and minimal abstraction, accepting weaker HMR and some feature gaps (top-level await, code splitting).
  • New features like built‑in tsconfig paths support are welcomed, but several criticize fragmented or inadequate documentation around Vite 8, Rolldown, and Oxc (e.g., JSX-in-.js configuration, manual chunks changes, Node import aliases quirks).

Broader Performance & Resource Waste Concerns

  • Thread frequently returns to how much compute is wasted: slow builds, Electron apps with huge memory usage, heavy self-hosted tools needing multi‑GB RAM.
  • Some argue the web and JS ecosystem systematically trade efficiency for developer convenience and marketing, and predict this era will be seen as highly wasteful.