51.6%.
That’s VS Code’s share among Rust developers today, down a sharp 10 points from 61.7% in 2022.
Look, if you’re knee-deep in code — especially Rust’s memory-safe wizardry — this isn’t just a blip. It’s a tremor. AWS, the cloud behemoth powering half the internet, just announced a “strategic investment” in Open VSX, the Eclipse-run registry that’s become the go-to for VS Code forks dodging Microsoft’s marketplace lockdown.
And here’s the electric part: AI-first editors like Cursor, Zed, and AWS’s own Kiro are flocking to it. Imagine the wild west of IDEs suddenly getting a neutral saloon where everyone grabs their extensions without Big Brother watching. Open VSX hit 300 million monthly downloads — that’s no small potatoes — and now it’s shifting to AWS infra in Europe, with a Canadian backup and fancy new verification to squash malware.
But.
Microsoft’s not playing nice. Their marketplace? Locked tighter than a vault. “Alternative products including those built on a fork of the Code-OSS Repository, are not permitted to access the Visual Studio Marketplace,” they say, blaming security and the hassle of running it for free riders. Chris Dias, ex-VS Code product head, called it out: no business case for a global service everyone mooches off. Fair? Maybe. But it reeks of the old Microsoft — gatekeeping to protect the empire.
Why Did Rust Devs Jump Ship from VS Code?
Zed exploded to 18.6% usage. That’s Rust-powered speed demon, feeling like a Ferrari next to VS Code’s truck. JetBrains’ Rust Rover dipped a tad, but the real story? AI’s crashing the party.
Traditional IDEs? They’re like horse-drawn carriages in the age of hyperloops. OpenAI’s been yelling it: agent-driven dev needs more than autocomplete. Microsoft crammed Copilot everywhere, but devs gripe — intrusive pop-ups, distractions mid-flow. Rust survey screams it: folks want lean, fast, AI-native tools.
Open VSX started in 2020 with GitPod (now Ona), a lifeline for forks like VSCodium and Theia. Now? Google Antigravity, Windsurf, Cursor — all in. Fewer extensions than Microsoft’s 93k behemoth, sure, but the hits are there (minus Redmond’s own). And that 2023 near-death scare? Eclipse’s John Kellerman begged for cash, warning shutdown by May. Companies rallied; now AWS and Cursor sponsor.
Paid tiers kicked in January — over 75 requests/sec? Pony up. Smart move for sustainability.
My bold call — and this is the insight you’ll not find elsewhere: this mirrors the PDF wars of the ’90s. Adobe locked down PostScript; open Acrobat PDF won because devs demanded portability. Open VSX? It’ll be the PDF of extension land by 2028, with AI auto-porting the rest. Microsoft’s spin on “security” won’t hold when agents roam free across editors.
Can Open VSX Topple VS Code’s Marketplace?
Short answer: not tomorrow. VS Code’s at 76% in Stack Overflow’s survey, crushing Visual Studio’s 30%. Monthly updates, cross-platform bliss. But cracks show. AI wave births rivals optimized for agents — think Zed’s GPU-accelerated rendering or Cursor’s code-gen magic.
AWS’s move? Genius. Europe’s their beachhead, hybrid setup screams reliability. New verification framework blocks fakes — timely, with supply-chain hacks everywhere.
“We will be forced to decommission the Open VSX registry by the end of May,” John Kellerman warned in 2023.
They didn’t. Now, 300 million downloads/month. That’s momentum.
Critique time: Microsoft’s PR paints forks as risky outliers. Baloney. It’s control. VS Code’s OSS base (Code-OSS) lets forks thrive, yet marketplace access? Nah. Hypocrisy fuels the fire.
Picture this: your AI agent, zipping code across editors, pulling extensions from a neutral hub. No vendor lock-in. That’s the platform shift — AI as the new OS, IDEs as plugins. VS Code decline in Rust? Harbinger. Expect it ripple to Go, Python next.
Developers, rejoice. Choice is back. AWS didn’t just fund; they bet on fragmentation as strength.
And yeah, Golang generics landed (not top demand), Veracode cries security’s toast in AI speed-runs, Cloudflare AI-ports Next.js APIs in a week — chaos breeds innovation.
One punchy para: The IDE market’s heating up like a supernova.
What Does AWS’s Play Mean for AI Dev Tools?
Strategic. AWS Kiro’s a fork — they need Open VSX healthy. Cursor too. It’s ecosystem chess: Microsoft dominates, but clouds crave open plumbing.
Rust’s canary in the coal mine. 51.6% VS Code? Zed at 19%. If Rust — efficiency obsessives — bails, who’s safe?
Bold prediction: 2027, Open VSX matches extension count via AI bridges. Agents generate ports on-the-fly. Microsoft’s stuffing AI in? Cute, but too late. The future’s modular, multi-editor swarms.
Energy here — it’s exhilarating. We’re not tweaking tools; we’re birthing a dev paradigm where code writes itself across playgrounds. VS Code? Great grandpa now.
Wander a sec: remember Vim vs. Emacs wars? This is that, but with trillion-param brains refereeing.
🧬 Related Insights
- Read more: Why Open Source Contributions Aren’t Charity—They’re a $2.6 Trillion Business Move
- Read more: Why This Streaming Analytics Site Ditched React for Vanilla JavaScript—and Won
Frequently Asked Questions
What is Open VSX and why AWS backing?
Open VSX is an open extension registry for VS Code forks, free from Microsoft’s restrictions. AWS’s investment funds European AWS-hosted infra, boosting reliability for AI editors like Cursor and Kiro.
Why VS Code declining in Rust survey?
Dropped to 51.6% from 61.7% as devs flock to faster, AI-native rivals like Zed (18.6%). Microsoft’s AI features feel bloated to speed-focused Rustaceans.
Will Open VSX replace VS Code marketplace?
Not fully soon — fewer extensions — but AI and sponsorships (AWS, Cursor) position it as the neutral hub for agent-driven dev, potentially matching scale by 2028.
