AI summary by TwinMind
VS Code Is Fighting Back (RIP Cursor?)
Theo - t3․gg
16m 12s
Background Context
- Cursor is fork of VS Code built for better AI editing experience
- Charges money for enhanced UX features that couldn't be done in VS Code extensions
- Speaker currently uses Cursor as primary editor
- VS Code fighting back with new update copying Cursor features
- Speaker is Microsoft investor (disclosed bias)
New VS Code Copilot Features Overview
- Attaching extra context to quick chat
- Generate tests command updates
- Configure custom code instructions
- Session summaries in chat history
- Longer context for code and chat
- Automatic references for recent files
- Natural language inline edits
- Generate debug configurations
- Generate test based on coverage
Quick Chat Context Attachment
- Can now pick files and send as context when asking Copilot
- Similar to Cursor's context features
Test Generation Feature
- Right-click function → "Generate Tests"
- Generated 51 lines of tests for 18 lines of code
- Used Jest framework with mocks, spies, error handling
- Speaker skeptical of AI-generated tests
- "If tests aren't written by human, losing value"
- "Point of tests is asserting human expectations"
- Tests didn't run properly due to:
- Missing Jest setup
- Import/export issues
- Alias resolution problems
Inline Chat Improvements
- Can type in editor and use current line as prompt
- Copilot detects when prompting vs writing code
- Automatically starts inline chat
- Speaker struggled to make feature work consistently
- Command palette integration available
Code Generation Instructions (Global Settings)
- Can set instructions added to every Copilot request
- Tested with "make sure all answers are type safe"
- Feature didn't work reliably in inline mode
- Worked in top-level chat but not everywhere
- Tested humorous settings:
- "Always respond with Python code"
- "Use inverse casing"
- "Respond in pig Latin"
Comparison Testing: VS Code vs Cursor
- Same prompt: "download image instead of zip if only one image in array"
- Both produced similar quality code
- Both had type safety issues (unchecked index access)
- Neither properly addressed type safety concerns
- Code quality roughly equivalent between tools
Chat History & UX Improvements
- User-friendly AI-generated names for chat sessions
- Similar to Arc browser's auto-naming feature
- Thumbs up/down feedback system for responses
- Slash commands in inline chat for specific behaviors
Overall Assessment
- VS Code improvements are "cool ideas" but not as good as Cursor
- Slash commands concept is "exciting"
- Quality gap remains between VS Code and Cursor
- Features work but inconsistently
- Speaker will continue using Cursor
- Acknowledges bias due to investments but claims objectivity
