Comment by atombender

I've been using Jetbrains IntelliJ IDEA as my main IDE for Go, Rust, TypeScript, etc. for the last 3 years, and this Christmas I switched to Zed, and I'm not looking back.

I was admittedly skeptical of Zed in the beginning, because they started out with so few features, and it seemed impossible to really switch permanently to it and still be as productive. The Jetbrains platform has got such an amazingly rich set of features and an uncanny ability to just nail the editor experience. It seems almost unthinkable that anyone would be able to compete, and for a long time Zed was very far behind, but this year I feel they're finally a viable alternative.

What ultimately pushed me towards Zed was performance and the sheer amount of work-stopping bugs. I would have days where Jetbrains would get unresponsive or extremely sluggish. Suddenly "undo" would stop working (!). Major and minor upgrades often introduced perplexing performance degradation. In short, I've wasted insane amounts of time on bugs and on filing detailed bug reports that are never looked at. That undo bug has been open for maybe a year now.

For all the bells and whistles, I think Jetbrains faces an intractable problem. It's just utterly unrealistic that they'll be able to solve everything unless they stopped all development to focus on just stability. The product is too big, too complex, too unwieldy, and too bloated. I was always allocating 16GB RAM to Jetbrains, and often had it sit there consuming 1000% (!) CPU. Zed chews up a couple of gigs at most, and rarely uses much CPU. There's a tendency for editors to get bloated as they evolve. This certainly happens with Atom. I'm really hoping Zed will stay lean.