Zed in particular, from the way it was described upon release, sounded like it should have been a JB competitor. Reality: It can't even move functions or structs!
A year or two ago, I finally gave up:
1. The IDE was simply too slow - notably slower and "heavier" than VS Code in particular - and it seemed to regularly get slower.
2. Bugs - from the complex (TypeScript constructs that tsc itself handles just fine while WebStorm's code analysis kept throwing false positives on) to the trivial and silly (failing to properly handle the <col> tag in React), and often staying open for years.
Meanwhile, VS Code just kept getting better, addressing the complaints I had with it while staying fast.
I work almost exclusively in TypeScript these days; as other commenters pointed out, I'm sure that JetBrains products are still great for other languages.
And their refactoring tools remain second to none. I'm profoundly disappointed in our industry that the VS Code developers apparently looked at JetBrains, with its arsenal of expertly crafted, deterministic, testable refactorings, and said, "Nope, we'd rather make everyone use inherently random language models for anything more complex than Rename Symbol."
The remote dev story is bad, it won't play nice with Nix environments, and high DPI support on Linux kept breaking on every other update.
I still miss the Git client sometimes, but Jujutsu has filled the gap.
For languages like kotlin, java and even python JB is still way ahead of the competition.
vscodium[0] might require some aftermarket bells and whistles to reach feature parity with jetbrains' "swiss army kitchen sink" approach but at least vscodium is not data-mining me.
At least, that was so in dynamic languages, like Python, and PHP, last I checked.
That's always been my experience. Not even close. One gives you legos that lets you make a plastic toy, and the other is an industrial machine shop for code.
I thought maybe I was holding VSCode wrong, though.
Likewise (Same with zed). I've given them a thorough try several times, assuming I was holding it wrong as you say based on conversations with others who use them effectively. I've reached the conclusion you say here each time.
I don't want to spend a lot of time finding, installing, and configuring the right combination of plugins to bring VS Code up to Webstorm level.
Also, I don't trust plugin/extension marketplaces anymore. There is lower exposure in having fewer dependencies.
I use Rider but need VS for some things.
But there's plenty of examples.