惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
云风的 BLOG
云风的 BLOG
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
D
Docker
H
Help Net Security
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Microsoft Azure Blog
Microsoft Azure Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
Tailwind CSS Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
月光博客
月光博客
C
Check Point Blog
S
SegmentFault 最新的问题
T
The Blog of Author Tim Ferriss
J
Java Code Geeks
M
MIT News - Artificial intelligence
B
Blog RSS Feed
MyScale Blog
MyScale Blog
大猫的无限游戏
大猫的无限游戏
Hugging Face - Blog
Hugging Face - Blog
腾讯CDC
美团技术团队
I
InfoQ
Blog — PlanetScale
Blog — PlanetScale

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Open VSX vs VS Code Marketplace — where should you publis...
dekidev · 2026-05-18 · via DEV Community

dekidev

I built Dusk Office for myself.

No seriously — I was the only user. Ever. It was just my personal theme that I used every single day while working on my projects. I liked how it looked, it felt premium, and it made my long coding sessions easier on the eyes.

One day I thought: why not just publish it? like all the cool kids do 😄

So I did. I pushed it to Open VSX and the VS Code Marketplace at the same time, mostly out of curiosity. I didn't expect much — there are already thousands of color themes out there.

Then I started seeing devs install it. Sometimes 200 downloads in a single day. That motivated me to push updates regularly. With my new AI colleague I could even ship two updates in the same day.

6 weeks later:

  • Open VSX → 5 200+ downloads
  • VS Code Marketplace → 56 downloads

Same extension. Same period. Zero promotion. No Reddit, no Twitter, nowhere.

I was just as surprised as you are right now.


Wait... what is Open VSX?

If you only use VS Code, you might not know Open VSX exists.

It's an open-source extension registry used by editors that can't access the official Microsoft Marketplace — think Cursor, VSCodium, Windsurf, Gitpod, Theia...

These editors have millions of users. And they all pull from Open VSX.

Honestly, I had no idea this registry even existed before I published.


Why the gap?

My theory:

Cursor and Windsurf users care more about themes.

They're the kind of devs who customize everything — their editor, their terminal, their workflow. When they look for a theme, they actually browse and try things.

VS Code users? A lot of them just stick with the default or grab the first popular theme they find (One Dark Pro, Dracula, etc.). The market is more saturated and harder to break into.

On Open VSX, there's less competition. A quality theme stands out faster.


What this means if you're building an extension

If your extension targets developer tools, themes, or productivity — publish on Open VSX first. The audience is smaller but more engaged.

If your extension is more mainstream or targets beginners — the VS Code Marketplace is still the bigger pond.

Ideally? Publish on both. It takes 5 minutes extra and the upside is real.


My next move

Now that I know Open VSX is where my audience lives, I'm doubling down — better screenshots, better description, more variants.

The VS Code Marketplace is still an untapped opportunity for me. 56 downloads means almost nobody has seen it there yet. Same product, fresh audience.

That's basically free growth waiting to happen. 🚀