AI summary by TwinMind
Copilot is so desperate, they made it free
Theo - t3․gg
28m 30s
Initial Skepticism and AI Tool Evolution
- Speaker admits initial skepticism about Copilot in 2021
- Made video expressing doubts about capabilities
- Changed mind after using for Advent of Code, achieved unprecedented leaderboard times
- Microsoft started charging for Copilot extension (unusual for editor extensions)
- Competition emerged with "quite a bit better" alternatives
- Microsoft's desperate attempts to compete:
- Introducing new models
- Breaking ChatGPT exclusivity to add Claude
- Adding new VS Code features
Savala Sponsor Segment
- Demonstrates Laravel app deployment process
- Features: automatic deploy on commit, multiple resource tiers ($5/month hobby tier)
- Cloudflare integration for CDN, DDoS protection
- Preview builds for pull requests, trunk-based development workflows
- Supports static/dynamic, JavaScript/PHP, MySQL/Redis
Speaker's Investment Disclosure
- Microsoft investor (largest position)
- Also invested in Cursor, Super Maven (acquired by Cursor), Pairis
- Acknowledges bias toward Satya/Microsoft
GitHub Copilot Free Tier Announcement
- Targeting 150+ million GitHub developers
- Features included:
- Chat for code explanation in natural language
- Multiple model selection (Claude 3.5 Sonnet, GPT-4o)
- Multi-file edits
- Third-party agents ecosystem
- Code completions
- Limits: 2,000 completions, 50 chat requests per month
- Speaker criticizes model selection as "leaky abstraction"
AI Tools Impact on Development Experience
- Positive aspects:
- Makes coding more fun by eliminating tedious tasks
- Handles boring parts (image resizing, math calculations, API integrations)
- Allows focus on creative/interesting work
- 2-3 hours now as productive as previous 8-12 hour sessions
- Concerns about junior developers:
- Risk of never developing fundamental skills
- Everything feels "unfun and dumb" when learning
- AI becomes crutch preventing skill development
- Similar historical concern when IDEs emerged (developers lost bash skills)
Hands-on Testing: VS Code vs Cursor
Initial Setup Issues
- VS Code extension broken after update
- Interface instability, crashes
- Basic functionality problems
Test 1: Simple Code Addition
- Task: Add "allows pasting images from clipboard" to existing tools
- VS Code Copilot:
- Failed to understand codebase context
- Required manual file selection
- Poor UX with overlapping interface elements
- Eventually worked but required significant manual intervention
- Cursor:
- Automatically read files and understood context
- Applied changes correctly without manual file selection
- Much faster execution
Test 2: Complex Feature Addition
- Task: Add border color detection to image processing tool
- VS Code Copilot:
- Hallucinated non-existent functions
- Generated broken code with incorrect API usage
- Required extensive manual fixes
- Save functionality broken (Command+S not working)
- Final result partially functional but buggy
- Cursor:
- Successfully implemented feature with proper file structure
- Created new utility file automatically
- Generated working UI with proper state management
- Auto-saved changes, cleaner implementation
Technical Issues Encountered
- VS Code extension API limitations severely restrict functionality
- Interface clipping and rendering problems
- Broken keyboard shortcuts
- Token burning from excessive context usage
- Hallucinated code patterns and incorrect function calls
Final Assessment
- Free tier generous due to Microsoft's financial resources (competitors can't match)
- VS Code Copilot significantly inferior to alternatives like Cursor
- Recommendation: use free tier if not paying, but paid alternatives superior
- Microsoft leading initially but "fumbled" the execution
- Competition forcing defensive moves (free tier as market share protection)
