JetBrains PyCharm vs Visual Studio Code
5 members list JetBrains PyCharm, up 4 in the last 12 weeks
8 members list Visual Studio Code, up 4 in the last 12 weeks
How has interest in each changed?
Collected from public datasets outside Stackness, not from stacks on this site. A series both tools have shares one chart and one scale, because its unit is the same for both. Data sources
Mentions, monthly
JetBrains PyCharm: Hacker News mentions: 9 mentions (2010) to 13 mentions (2026)
Visual Studio Code: Hacker News mentions: 1 mention (2015) to 148 mentions (2026)
Imported from Hacker News mentions
Installs, monthly
JetBrains PyCharm: Homebrew analytics installs: 2,000 installs (2026) to 1,200 installs (2026)
Visual Studio Code: Homebrew analytics installs: 41,914 installs (2026) to 25,816 installs (2026)
Imported from Homebrew analytics
Questions asked, monthly
JetBrains PyCharm: Stack Exchange data explorer questions asked: 1 question (2010) to 3 questions (2026)
Visual Studio Code: Stack Exchange data explorer questions asked: 1 question (2010) to 20 questions (2026)
Imported from Stack Exchange data explorer
Usage share, yearly
JetBrains PyCharm: Stack Overflow developer survey usage share: 9.12 % of respondents (2017) to 15.14 % of respondents (2025)
Visual Studio Code: Stack Overflow developer survey usage share: 19.05 % of respondents (2017) to 76.37 % of respondents (2025)
Imported from Stack Overflow developer survey
Pageviews, monthly
JetBrains PyCharm: Wikipedia pageviews: 6,847 views (2015) to 4,633 views (2026)
Visual Studio Code: Wikipedia pageviews: 6,424 views (2015) to 32,303 views (2026)
Imported from Wikipedia pageviews
Who uses both?
No member lists both JetBrains PyCharm and Visual Studio Code yet.
1 member moved from JetBrains PyCharm to Visual Studio Code and 0 from Visual Studio Code to JetBrains PyCharm in February 2026.
What do people pair them with?
Tools that members list in the same stack as each of them.
Paired with both
Only with Visual Studio Code
How do they differ?
VS Code took over the leadership at some point.
Written by Sergei Gordeichuk,