The IDE debate is eternal. VS Code fans say it's fast and extensible. JetBrains loyalists swear by deep language support. And now Cursor is the new challenger, riding the AI wave. The Stack Overflow Developer Survey consistently ranks VS Code as the most popular editor, while the JetBrains Developer Ecosystem Survey shows strong loyalty among its users. But surveys measure sentiment, not reality.
What do developers actually use when they sit down to work? Not what they tweet about. Not what they starred on GitHub. What they code in, hour after hour, day after day.
We have the data. thousands of hours of tracked coding time across 100+ B2B companies, broken down by IDE.
The Data Source
PanDev Metrics collects IDE heartbeat data through editor plugins. Every coding session is tagged with the specific editor or IDE being used, the language, and the timestamp. This gives us precise usage data — not survey responses, not download counts, but actual hours spent coding.
Our dataset:
- 100+ B2B companies (enterprise, mid-market, startups)
- nearly 1,000 individual users on the platform
- active B2B developers generating heartbeat data
- thousands of hours of IDE activity across all tracked IDEs
- Data period: production data as of early 2026
This is the same dataset behind our research on how much developers actually code and top programming languages by coding time.
The Top 3 IDEs by Real Usage
| IDE | Total Hours | Active Users | Hours/User |
|---|---|---|---|
| VS Code | 3,057h | 100 users | 30.6h |
| IntelliJ IDEA | 2,229h | 26 users | 85.7h |
| Cursor | 1,213h | 24 users | 50.5h |
These three numbers tell a story that no survey can capture. Let's unpack it.
VS Code: The People's Choice
VS Code dominates by user count. 100 out of our tracked users — more than both competitors combined — use VS Code as their primary editor. With 3,057 hours of total coding time, it's the most-used IDE in our dataset by a wide margin.
Why VS Code Wins on Adoption
- Zero cost: No license negotiations, no budget approvals needed
- Language agnostic: Works for TypeScript, Python, Java, Go, Rust — everything
- Extension ecosystem: Whatever you need, there's an extension for it
- Fast startup: Opens in seconds, even for large projects
- Remote development: SSH, containers, and Codespaces support built in
The VS Code Caveat
Notice the hours per user: 30.6h. This is the lowest among the top 3. There are two possible explanations:
- VS Code attracts a wider range of users, including those who code less frequently (managers, designers, DevOps engineers who occasionally edit config files)
- Some VS Code users are lighter coders who supplement with other tools
This doesn't mean VS Code users are less productive. It means VS Code's user base is broader and more diverse than JetBrains or Cursor.
IntelliJ IDEA: The Enterprise Workhorse
IntelliJ has only 26 users in our dataset — but those 26 users logged 2,229 hours. That's 85.7 hours per user, nearly three times the per-user average of VS Code.
The IntelliJ Profile
IntelliJ users are almost exclusively Java and Kotlin developers working on large enterprise codebases. They tend to be:
- Senior developers and architects
- Working on long-lived, complex backend systems
- In companies that provide JetBrains licenses as standard tooling
- Heavy users of IntelliJ-specific features: refactoring tools, database integration, debugging
Why IntelliJ Users Code More Per Person
The 85.7 hours/user figure reflects the profile of IntelliJ's user base in enterprise settings: dedicated backend developers who spend most of their working hours in the IDE. They're not switching between tools. They live in IntelliJ.
This concentration is both IntelliJ's strength and its limitation. It's the best IDE for deep Java/Kotlin work. But it hasn't captured the broader developer population the way VS Code has.
The JetBrains Ecosystem Note
Our data specifically tracks IntelliJ IDEA. JetBrains also offers WebStorm, PyCharm, GoLand, and others. Some developers in our dataset may use other JetBrains products that are tracked separately. The total JetBrains ecosystem share is likely higher than IntelliJ alone suggests.
Cursor: The AI-Native Newcomer
The most interesting story in this data is Cursor. With 24 users and 1,213 hours, it's already the third most-used IDE in our dataset — a remarkable achievement for a product that's only a couple of years old.
Cursor by the Numbers
- 24 users — comparable to IntelliJ's 26
- 1,213 hours — already 40% of VS Code's total with 24% of the users
- 50.5 hours per user — higher than VS Code, lower than IntelliJ
Who's Using Cursor?
Cursor users in our dataset tend to be:
- Early adopters and tech-forward developers
- Working primarily in TypeScript, Python, and newer stacks
- Often in smaller, more agile companies
- Developers who have invested in AI-assisted workflows
The Cursor Effect
What makes Cursor's numbers notable is the trajectory. It went from zero to 24 users and 1,213 hours in a B2B enterprise context — not hobby developers, not students, but professional engineers at companies paying for PanDev Metrics.
This suggests that AI-native editors are moving from curiosity to daily driver status. The question isn't whether AI-assisted IDEs will gain share. It's how fast.
[Coding activity heatmap by hour and day]
Activity heatmaps reveal not just which IDE developers use, but when they are most actively coding throughout the day and week.
What the Data Tells Us About IDE Switching
One pattern we observe: IDE switching is rare at the individual level. Most developers in our dataset use a single primary IDE for 90%+ of their coding time. The exceptions:
- Developers who use VS Code for frontend work and IntelliJ for backend work in polyglot projects
- Developers who are gradually migrating from VS Code to Cursor
- DevOps engineers who use VS Code for most work but occasionally open a JetBrains IDE for specific tasks
This "IDE loyalty" means that the competition isn't about winning over existing users day-to-day. It's about being the choice for new developers and new projects. Evans Data Global Developer Population estimates put the worldwide developer count at ~30 million+ — and each one of them makes an IDE choice that largely sticks.
The Real Comparison: It Depends on What You Do
The "best IDE" question is misleading because each IDE serves a different profile:
Choose VS Code If:
- You work across multiple languages
- You value customization and extensions
- You want the largest community and ecosystem
- You need remote development capabilities
- Budget is a constraint
Choose IntelliJ (JetBrains) If:
- You work primarily in Java, Kotlin, or other JVM languages
- You need deep refactoring and debugging tools
- You work on large, complex enterprise codebases
- Your company provides JetBrains licenses
- You value "it just works" over configurability
Choose Cursor If:
- AI-assisted coding is core to your workflow
- You work in TypeScript, Python, or modern stacks
- You're willing to be an early adopter
- You want inline AI suggestions and chat integrated into your editor
- You're transitioning from VS Code (Cursor is VS Code-based, so the switch is painless)
Implications for Engineering Leaders
Don't Mandate a Single IDE
Our data shows that each IDE has a distinct user profile. Forcing all developers onto one IDE means some will be working with a suboptimal tool. The productivity cost of using the wrong IDE for a specific job outweighs any standardization benefit.
Budget for JetBrains Where It Matters
If you have a Java/Kotlin team, JetBrains licenses pay for themselves. The 85.7 hours/user figure shows these developers live in their IDE. A $200/year license for a tool someone uses 80+ hours is trivial.
Watch the Cursor Trend
Cursor's growth from zero to 24 enterprise users deserves attention. If AI-assisted coding delivers even a 10-15% productivity improvement, the ROI of Cursor licenses for your team could be significant. Consider running a pilot.
Track IDE Usage, Don't Guess
Most engineering leaders don't know their team's actual IDE distribution. They assume "everyone uses VS Code" or "we're a JetBrains shop." The reality is often more varied. Knowing what tools your team actually uses helps you make better decisions about tooling investments, plugin development, and developer experience.
The Future: Convergence or Specialization?
Our data suggests we're heading toward a three-way market:
- VS Code as the universal default for general-purpose development
- JetBrains as the premium choice for enterprise language-specific deep work
- AI-native editors (Cursor and upcoming competitors) as the future for AI-augmented development
The wildcard is whether VS Code's AI extensions (GitHub Copilot, etc.) can close the gap with Cursor's native AI integration. We explore this dynamic further in the AI copilot effect on coding time. If they can, Cursor's growth may plateau. If not, we could see a significant migration of VS Code users to AI-native editors over the next 1-2 years.
Either way, the IDE war of 2026 has three real contenders — and the data shows each has a legitimate place.
Track your team's real IDE usage. PanDev Metrics shows which editors your developers actually use, how many hours they spend in each, and how usage is trending over time.
More from PanDev Metrics Blog
- How Much Do Developers Actually Code Per Day?
- Top 10 Languages by Actual Coding Time
- The AI Copilot Effect: How AI Changed Coding
- Focus Time: Why 2 Hours = 6 Hours Fragmented
- Monday vs Friday: Day of Week Productivity
PanDev Metrics — Engineering Intelligence platform. Track real coding time across VS Code, JetBrains, Cursor, and 8 more editors.
