JetBrains Doesn’t Want Me To Give This Talk
summary
Explains why JetBrains balances AI work with IDE reliability, lists actual tools and timelines: an AI assistant, agentic tooling Juny, and a new web coding product Kinetto are live or in trials; the team runs AB tests on a homegrown Type Engine with a plan toward 2025.3 for TypeScript. Shares concrete metrics: an Appex perf threshold of ~300ms tolerable vs 500ms frustrating, monitors regressions (2024.1 → 2024.2 rollback), and reports fixing thousands of bugs while shipping ~200 features.
AI-written summary · about
chapters (10)
- 0:00This talk isn’t a product pitch
- 3:56JetBrains’ AI focus extremes
- 7:53AI won’t replace developers
- 8:14WebStorm bug reports transparently
- 13:54Bug and feature prioritization drivers
- 16:43WebStorm performance metrics
- 20:40Report performance issues
- 22:09Memory and startup performance
- 26:19Why not LSP everywhere
- 30:11Closing thoughts
related talks
07mA quick word about JetBrains now and later
52mResistance Is Futile
41mAI Tooling for Scala Developers - What JetBrains Brings to the Table
41mWill AI Assistant make developers redundant?
06h 30mJetBrains Plugin Developer Conf 2025
50mDeveloper Productivity – DIY (with LLM) or How I Learned to Stop Worrying and Love the AI
47mAI, Automation & DevEx: Fueling High-Velocity Engineering
08mAI inside the IDE