The tool where all the world's software gets written suddenly turned into a battlefield. Not over design. Over who finishes the programmer's sentence first.
A code editor is the craftsman's workbench. The tools are laid out within reach, you can see right away which board is warped, which joint doesn't fit. The editor underlines mistakes as you write them, shows what someone else's code does without opening it line by line, connects directly to Git (the system that keeps every version of the code) and keeps the command terminal one click away. The difference between a good and a bad such tool isn't aesthetic - it directly decides how fast you get from idea to something that works.
VS Code came out of Microsoft in 2015 on a simple bet: if the editor is free and open, programmers will choose it themselves, without IT forcing it on them. The bet paid off. By the latest annual surveys among programmers it remains by far the most-used tool in the trade, well ahead of everything else. Much of it is open source, meaning anyone can build their own version on top of its scaffold without asking Microsoft's permission.
That's exactly what opens the door for JetBrains. The company makes separate, paid editors for each major language: IntelliJ IDEA for Java, PyCharm for Python, WebStorm for JavaScript. They're not free and don't pretend to want to be. Their argument is different: when the project is a million lines of code, built up over years, the free workbench isn't enough anymore. You need deeper analysis and refactoring tools, and companies with budget pay for them without thinking twice.
Xcode stands apart. For Apple it's not a choice - it's a condition. It's free, but it only runs on Mac and it's the only path an app takes to reach the App Store. You have no alternative if you're making anything for iPhone. That's why Apple isn't in a hurry to compete in an open market. There's a closed door, and everyone who wants through it goes by its rules.
The real battle of the last year is elsewhere: which editor writes the code for you. Cursor, literally a copy of VS Code with artificial intelligence built in from the start, reached a valuation of 29.3 billion dollars (end of 2025), because programmers massively preferred it over the original. Microsoft answered by turning its own GitHub Copilot (the AI assistant inside VS Code) from line autocomplete into something that turns a given task straight into finished code. JetBrains added its own AI assistant. A brand-new editor even appeared, Zed, written from scratch on the idea that any outside AI should be able to plug into it. Nobody dares fall behind, because the cost of switching is zero: your settings carry over with one button, and loyalty to a specific program no longer exists.
I've tried something like this
I've written in VS Code so long my fingers find the keyboard shortcuts before my brain has asked for them. It's not sentiment. Muscle memory - the same kind with which a designer reaches for the mockup knife, without looking at the table. When the AI-powered editor started finishing my sentences, the first feeling wasn't delight - it was mild irritation, like someone touching your tools on the table while you work.
Then I got used to it and, honestly, it got faster. But there's one thing I'm not ready to give up: I don't let the editor decide instead of me what has to happen, only how to get there faster once I've already decided. The workbench can be smarter. The craftsman standing at it stays the same.