They both work very well. My only complaint is that you can't use them to generate commit messages using the Git Panel (have to do it inside the Agent Thread instead), and /compact seems to have issues so you will often need to start a new thread (this wasn't an issue in the past so hopefully it will get fixed soon).
i investigated this yesterday and there is one cmake extension. It gives basic support to cmake. Not as neat as vscode/jetbrains/qt/vs but it works. It is depends on CMakePresets.json and has no gui etc.
I can’t relate to that, I’ve also struggled with this decision for quite some time, but I’ve gotten used to it. What I hate is that it doesn’t open several search tabs if I need to look for several things at once.
Personally I don't hate tab. Sometimes even it's more convenient to have a tab on the side with all the state, instead of reopening modal.
What I hate though is really unintuitive and "non-standard"[1] shortcuts in search tab.
For example "find in project": cmd+shift+f
Whereas for "find and replace in project" I'd expect: cmd+shift+r , but it's: first toggle find, then toggle find and replace. Ok, absolutely fine, but the keyboard shortcut to toggle is: cmd+shift+h - I never can remember it.
When already searching, for my "convenience", if I'd like to adjust my search or search for something new, I click cmd+shift+f and I am focused back to find input, but here's the kicker. Input have automatically changed to what word was under my cursor. So if I was looking for some long or weird string, I need to retype it again or find and copy/paste it again.
#first-world-problems though.
I got tired of babysitting vim/neovim and all it's plugins and use Zed for most of my editing. It has pretty good vim binding support and maybe I just need to remap some key bindings to have better search experience. Zed is much better at emulating vim than Cursor/VSCode.
[1] there's no standard obviously, but some things are the same/similar across most programs.
I was like: "it should be Ctrl+Shift+H, of course, right?"
So different tastes :-)
What you describe later is "Auto-populate the find dialog with current text under cursor". VSCode has a setting for that; I guess Zed will eventually end upnadeing one too.
If the idea of hiding extra Markdown elements or making it more WYSIWYG appeals to you, maybe we can put more eyes on some kind of feature request. I've seeing several comments come at this from different angles: ?id=47950471 ?id=47950748
How is their emacs keymap support? I tried VSCode for a while but switched back to emacs because it was so slow and the keymap was not very good. I've been intending to try Zed but emacs is working well enough so the motivation isn't really there yet..
The only thing that bothers me about Zed is the theme. It's so bland it actually gives me reading difficulties. I'd be surprised if some of the color combinations don't pose an accessibility issue. Grey text on grey background is quite the choice.
Congratz to the team. I really like zed and started using it quite early, loved the text threads and was using them a lot as I don't think llms fit in a box of only agents, they were a nice way to manage conversations, work through them, edit responses to lead the agent better, copy-paste full text, sad to see them go (text threads).
I'm trying right now the ACP with my own agent and I'm of mixed opinions but that's maybe because I care how my agent works. I believe that for the agent view a plain buffer with small ui elements would be the best ui for an agent conversation but I may have been spoiled by their text threads. I may spin a personal fork but the thought of tens of mins of compile time isn't that attractive.
Edit: I realized I started moving to terminal based editors like helix due to agents: claude -> codex -> custom pi, with the open sourcing of warp I was considering making a native integration for warp + pi but now I'm thinking zed's text threads (~17k lines) + pi might be a better way, any thoughts or ideas?
Good for them, but I wish they'd hurry up and catch up on some of the big missing features. Really hoping they'll accept my PR to add the missing call hierarchy feature before the GitHub issue turns 2 years old :)
Shortcuts still don't work on non-Latin keyboard layouts on Linux. For people who use languages with non-Latin writing systems, this is a show-stopper.
(there is, of course, a rich tradition of text editors with the same issue, including Vim and Emacs. They 1) have an excuse; 2) provide both workarounds and their own input method systems. Having this in a new program is nuts.)
Congrats to the Zed team! I really like your editor and it works surprisingly well, althought there are a few rough edges still with the python experience.
The debugger in Python FastAPI and mainly Django is not working as expected. Hopefully soon will be fixed.
Congrats guys! I've been using zed since a few months ago, I would consider myself a "light" user but I do enjoy the experience. My only sour point would be the not so smooth integration with claude code. But I've learmt to live with it for now
Feature-wise, Zed is still far from VS Code, but for me, the change has been worth it for the performance increase alone. I'm really happy with Zed, and I think it has a bright future ahead. Congratulations on the 1.0 release!
Zed is a durable piece of software, rather than the current trend of cheap disposable software. Regardless of whether humans or agents use a tool like this, durability is a benefit for both.
Congrats to the Zed team! I've been using a combination of Zed + Gram [1] (which I predict may lag behind this 1.0 release in features/fixes). They are both nice, fast editors. However, I switched to Sublime Text 4 again recently and... I'm surprised to see how much clunkier Zed feels than Sublime. I can't put my finger on it, but Sublime, although lacking in features, feels considerably more polished and performant.
I really want to like Zed because they've clearly put so much work into it, but so far I've been sticking with Sublime. I have several large PHP projects that were started in the 2010-2020 era, and Zed will highlight and complain about all sorts of minor things that were standard PHP fare at the time: functions without return types, for example. My code (which works fine) looks like an ocean of red when I view it with Zed, and turning all those warnings off is not trivial.
For each kind of warning, I wish there was a button that said "don't warn me again about issues like this one in this project." Then I could keep the interesting warnings (like undeclared variable) and ditch the ridiculous ones.
I love Zed, but I hear you. It's a very fast and capable editor with lots of IDE features, but it's lacking comfortable ways of tuning it for specific projects. (This is a problem with every general purpose, everything-to-everyone kind of IDE versus stack "native" IDEs that are geared toward the one true way of developing for particular target.) The configuration file structure is arcane, and it certainly not clear what the boundaries are between language feature configuration, LSPs, built-in and third-party code quality tools, etc.
I eat the cost of configuring it manually when I start up something new because it's just not that big of deal, even when you're like me, working across myriad languages and frameworks and organization with varying standards. It's not ideal, but it's not deal-breaker.
I do wish that there was a better way to definitively set it up a particular way and know that it is doing what you want it to do. I want something like presets/profiles. If I'm working with typescript, I want to be able to set it up to use a specific version of tsc, eslint, prettier; I also want to be able to create a different one with biome; I want it to work correctly whether I have my source in the project root or in a sub directory or in a monorepo tree.
Fairness to Zed: it is difficult to support all of these permutations, but I do think that they ought to be able to do something better to abstract these things and make the reusable.
I still stick with Sublime because when I give them money they haven’t given me reason to believe they’re going to waste that money putting in AI slop features I don’t want.
I've worked with mostly PHP from this era, or at least developers that are from this era. The code still runs fine, and not having things like return types don't make the code less able to run (just not as easy to catch bugs).
I haven't used Zed, but can you choose the PHP version, or point to a PHP executable for warnings/errors? I know in VS Code, you point to the PHP executable for the version you are using, to catch errors. I haven't created a new PHP project in quite some time, but I did work on many older PHP projects, and never had this issue with VS Code. I suspect even if you don't go about it this way, there has to be configuration to specify what is and isn't an error vs. warning.
Zed felt it had the right to download, install, and run node.js without any permission just to run some LSP (which I don't even use). When I mentioned it here, the devs said that they felt that was fine because their priority was to make things seamless for users such that they don't have to install the LSP manually. Sublime Text, on the other hand, has never installed anything I haven't explicitly asked it to.
I'm sticking with Sublime Text, as its developers actually respect boundaries on my computer.
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.
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.
277 comments
[ 3.4 ms ] story [ 121 ms ] threadWhen you search, Zed opens a new tab, which I hate. Sometimes I just want to have a quick glance at some code and close the search using escape.
Telescope style search in vim, helix or JetBrains tools is so much better.
https://github.com/zed-industries/zed/pull/46478
What I hate though is really unintuitive and "non-standard"[1] shortcuts in search tab.
For example "find in project": cmd+shift+f
Whereas for "find and replace in project" I'd expect: cmd+shift+r , but it's: first toggle find, then toggle find and replace. Ok, absolutely fine, but the keyboard shortcut to toggle is: cmd+shift+h - I never can remember it.
When already searching, for my "convenience", if I'd like to adjust my search or search for something new, I click cmd+shift+f and I am focused back to find input, but here's the kicker. Input have automatically changed to what word was under my cursor. So if I was looking for some long or weird string, I need to retype it again or find and copy/paste it again.
#first-world-problems though.
I got tired of babysitting vim/neovim and all it's plugins and use Zed for most of my editing. It has pretty good vim binding support and maybe I just need to remap some key bindings to have better search experience. Zed is much better at emulating vim than Cursor/VSCode.
[1] there's no standard obviously, but some things are the same/similar across most programs.
So different tastes :-)
What you describe later is "Auto-populate the find dialog with current text under cursor". VSCode has a setting for that; I guess Zed will eventually end upnadeing one too.
I’m hoping the roadmap contains support for even more things that extensions can do, such as rendering images or Markdown in-editor.
I'm trying right now the ACP with my own agent and I'm of mixed opinions but that's maybe because I care how my agent works. I believe that for the agent view a plain buffer with small ui elements would be the best ui for an agent conversation but I may have been spoiled by their text threads. I may spin a personal fork but the thought of tens of mins of compile time isn't that attractive.
Edit: I realized I started moving to terminal based editors like helix due to agents: claude -> codex -> custom pi, with the open sourcing of warp I was considering making a native integration for warp + pi but now I'm thinking zed's text threads (~17k lines) + pi might be a better way, any thoughts or ideas?
(there is, of course, a rich tradition of text editors with the same issue, including Vim and Emacs. They 1) have an excuse; 2) provide both workarounds and their own input method systems. Having this in a new program is nuts.)
The debugger in Python FastAPI and mainly Django is not working as expected. Hopefully soon will be fixed.
That seems risky.
Despite promising it for years and every comparable product having it.
Whenever I think to myself “yikes that sounds too hard”, my next thought is “well, Zed team could probably do it”.
Congrats to the team
[1] https://gram.liten.app/
For each kind of warning, I wish there was a button that said "don't warn me again about issues like this one in this project." Then I could keep the interesting warnings (like undeclared variable) and ditch the ridiculous ones.
I eat the cost of configuring it manually when I start up something new because it's just not that big of deal, even when you're like me, working across myriad languages and frameworks and organization with varying standards. It's not ideal, but it's not deal-breaker.
I do wish that there was a better way to definitively set it up a particular way and know that it is doing what you want it to do. I want something like presets/profiles. If I'm working with typescript, I want to be able to set it up to use a specific version of tsc, eslint, prettier; I also want to be able to create a different one with biome; I want it to work correctly whether I have my source in the project root or in a sub directory or in a monorepo tree.
Fairness to Zed: it is difficult to support all of these permutations, but I do think that they ought to be able to do something better to abstract these things and make the reusable.
I haven't used Zed, but can you choose the PHP version, or point to a PHP executable for warnings/errors? I know in VS Code, you point to the PHP executable for the version you are using, to catch errors. I haven't created a new PHP project in quite some time, but I did work on many older PHP projects, and never had this issue with VS Code. I suspect even if you don't go about it this way, there has to be configuration to specify what is and isn't an error vs. warning.
I'm sticking with Sublime Text, as its developers actually respect boundaries on my computer.
But it is not for me. Multiple issues on Linux and high memory usage makes it a worse alternative to vscode and jetbrains.
Maybe it's better on OSX, but I dont use that anymore and why use an editor that treats your platform as a second class citizen?
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.
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