If Vite, Bun and uv were just "make builds faster" projects, then maybe the returns are diminishing. But the acquisitions by Cloudflare, Anthropic and OpenAI suggest this layer is becoming more strategic, not less.
These tools sit in the software supply chain: dependency resolution, project structure, tests, builds, runtimes, deployment paths and increasingly AI-agent execution loops. They define the default path for building software, and they are where AI-generated code gets tested against real dependencies, builds, tests and deployment constraints.
So I don’t think they’ve achieved all they meaningfully can. The value is shifting from raw build speed to control over the workflow layer where software is assembled.
I haven’t used Claude Code much, but I found Codex extremely frustrating. It doesn’t pay attention to anything in AGENTS.md, it’s completely incapable of removing code and is frustratingly defensive.
If you use it, the codebase constantly grows. Even when you explicitly instruct it to remove something, you always end up with more lines of code in the project than before the instruction. Also (I used it for Python and TypeScript) the code was littered with getattr(...), .get(...), isinstance(...), and TypeScript equivalents (typeof, ...). Even though I religiously type‑annotate everything.
If Vite, Bun and uv were just "make builds faster" projects, then maybe the returns are diminishing. But the acquisitions by Cloudflare, Anthropic and OpenAI suggest this layer is becoming more strategic, not less.
These tools sit in the software supply chain: dependency resolution, project structure, tests, builds, runtimes, deployment paths and increasingly AI-agent execution loops. They define the default path for building software, and they are where AI-generated code gets tested against real dependencies, builds, tests and deployment constraints.
So I don’t think they’ve achieved all they meaningfully can. The value is shifting from raw build speed to control over the workflow layer where software is assembled.