Side by side
Visual Studio Code vs Cursor
Visual Studio Code
53 positive (61%) · 13 mixed (15%) · 21 negative (24%)
Trust + time weighted: +39%
AI summary — not a quote
Visual Studio Code (VS Code) is widely regarded as a highly optimized and versatile editor that serves as a lighter alternative to full IDEs like Visual Studio. While it remains a staple for web development and scripting, recent user sentiment is sharply divided. A significant portion of the community is frustrated by what they describe as 'AI-ification,' where recent updates prioritize LLM features and AI chatboxes over core bug fixes and traditional editor improvements.
Pros
- Highly optimized performance for an Electron-based application.
- Extremely versatile, supporting a wide range of languages from TypeScript to PowerShell.
- Lighter and less resource-intensive than full IDEs like Visual Studio.
- Seamless integration with AI tools like GitHub Copilot for developers who favor AI-assisted coding.
Cons
- Aggressive focus on AI features in recent updates, which some users view as bloat.
- Global search is frequently described as confusing or inferior to competitors like PhpStorm.
- New AI features have been known to hijack existing keyboard shortcuts and UI elements.
- Relies heavily on external plugins and SDKs for core features like debugging and syntax highlighting.
Top excerpts
Vs code, btw, runs perfectly fine on Linux
From VS Code, where every update is 90% some LLM stuff
I code on it in VS Code (Rust, Python, Java)
Grab VS Code and Python/Java (/react, whatever), then start programming the things you actually want to do.
I have to use VS Code on Linux and it's 100% not the same experience. Not saying it's terrible but I'd prefer if straight VS was compatible instead
Cursor
36 positive (62%) · 11 mixed (19%) · 11 negative (19%)
Trust + time weighted: +44%
AI summary — not a quote
Cursor is widely regarded as a highly integrated AI code editor that excels at codebase-aware prompting and rapid prototyping, often referred to by users as "vibe-coding." While many developers report significant speed increases and praise its auto-complete as best-in-class, a vocal segment of users finds the tool can become a hindrance. These users report that the AI can be overzealous, occasionally deleting functional code or requiring more time to troubleshoot unintended suggestions than it saves in writing.
Pros
- Deep integration with repository context allowing for code-aware prompting
- Superior auto-complete performance compared to many market competitors
- Effective at "vibe-coding" and rapid project building
- Streamlined error fixing by pasting logs directly into the editor
Cons
- Can be overzealous, sometimes deleting good code while attempting updates
- Potential for productivity loss due to frequent troubleshooting of AI suggestions
- Chatbot assistant performance reported by some to be inconsistent or degrading
- May ignore existing project conventions, such as opting for external CSS over Tailwind
Top excerpts
It can also enrich your prompt with more details so you don’t have to build a 5 paragraph prompt from scratch. It’s tightly integrated into whatever workflow. Take Cursor for example.
the staff/principal engineers are slinging PRs like never before thanks to cursor and Claude
When working across Claude Code, Cursor, or Freebuff CLI (which uses GLM 5.2 sessions), raw conversational prompts frequently suffer from context degradation after multiple roundtrips.
This is not meant to replace quick coding assistants. For small edits, Cursor, Claude Code, OpenCode directly, etc. are faster and simpler.
host-agnostic setup: works anywhere that can load skills from a directory (Claude Code, Cursor, Hermes, etc.)