Hey, support engineer at Zed here.

If you have a reproducible setup for a bug we don't know about, we'd love to get a proper report of it.

You can schedule 15mins with me here: https://calendar.app.google/fyLQkqvne7EdvR8XA

On MacOS I never really felt there was a noticeable performance difference to using Zed vs VSCode. I still like the idea of it being Rust/GPU based but just like those GPU optimized terminals (Kitty, Alacritty, etc) the difference is usually pretty marginal for day to day stuff.

The only time VSCode gets slow is if you use a bunch of poorly written plugins, which hasn't been an issue for me in years. It's just like Chrome, chrome is extremely fast as a base but you can mess it up by not being careful with what you add to it.

I still plan to revisit Zed in another year or so once it progresses further, as I find it's still behind Cursor in many ways.

So I'm not so sure how you arrived at your conclusion of Zed having higher memory use than VSCODE but in testing just now that's not at all close to true.

Zed for me on my Linux machine opened to a massive C++ project (the Ladybird browser if you were curious) is (not including LSP or extension processes) using around 480MB of memory.

VSCode on the other hand with nothing open but a 20 line JSON file is (again not including any LSP or extension processes) using around 920MB of memory as reported by its own builtin task manager thing.

I suppose 480MB for a text editor might be a tad high but calling it worse than VSCode is a massive stretch.

I've personally found it uses significantly less memory on large projects than VSCode. VSCode has historically been nigh-unusable for me on Linux, it gets incredibly sluggish.