Live data from Hacker News

Claude Code: Now in Beta in Zed

zed.dev

151–160 of 431 posts

Re: Claude Code: Now in Beta in Zed

#151
post #126

Earlier quoted context omitted.

Seems like a reasonable trade-off to me. I'm happy for them to have a sustainable business model and people seem quite willing to pay monthly for AI. As long as they keep the free version and the ability to disable AI features then I think everyone wins.

> As long as they keep... The thing is, they will have to switch to maximizing monetization (or die trying). Those investors are ultimately in control, and while they are happy to gain market share for now, that's what they will demand in the future. They will keep a free version for as long as it's working for them, but you will be monetized, one way or another, sooner or later, and you might not enjoy it.

Agreed, but Zed is open source so I think that does offer some long term protection to users who like the editor and don't want AI.

Re: Claude Code: Now in Beta in Zed

#152

I am sure Zed is great and I appreciate the effort put in to create it, but nowadays I just cannot imagine switching from VSCode to something else. In my limited understanding, none of the existing alternatives offer anything (and often misses at least something) truly innovative or anything else that VSCode extension wouldn't solve. On VSCode I have about 15 different profiles setup, each with different settings and…

I wanted to like VSCode but it has enough input latency on my machines that it's not that enjoyable when I'm "locked in". Also if I'm running a bunch of services in Docker on MacOS (which means they're running VMs sigh) the overhead of VSCode is just too much and the system starts swapping constantly grinding the whole thing to a halt. I also find configuring it a pain. Every configuration pane feels ad-hoc and not part of a holistic, configurable system. Emacs has lots of crusty bits and an annoying event loop that you have to really work around but is designed a lot more holistically than VSCode.

Zed to me feels like a great batteries-included editor and I still run it as my non-emacs alternate editor. I wish its configuration was a bit more discoverable (especially with configuring linters/formatters), but it's 95% of what I need 95% of the time.

Re: Claude Code: Now in Beta in Zed

#153
post #10

Zed is so great, I do wish they would focus just a little bit more on bringing the UI just a bit more up to parity with VS Code, I would switch full time.

Anyone running this on Linux? I find it works fairly poorly there. To be fair, vscode is also not great for me (especially vim mode) on Linux.

Running on Linux here. Working great for me. If you are referring to font rendering, unfortunately the Rust ecosystem for it is still young, so there are improvements to be made.

Re: Claude Code: Now in Beta in Zed

#154

Earlier quoted context omitted.

What do you feel is missing from the UI?

Their font rendering looks awful on non-high dpi displays, and the devs don't seem to care at all. https://github.com/zed-industries/zed/issues/7992

I won't use zed for this very reason.

Re: Claude Code: Now in Beta in Zed

#155
post #144

Earlier quoted context omitted.

>If you don't feel that VSCode is slow, it's because you are used to it. I don't think this is a fair claim. When you start doing an apples to apples comparison, that is to say make full use of IDE and auto-completion features it's difficult to see a difference given that the latency and speed of the plugins starts to dominate any millisecond difference in input latency or rendering speed.

No. When a press a character key on my keyboard, it should appear in my editor immediately. All other IDE features like auto-completion happen asynchronously.

> When a press a character key on my keyboard, it should appear in my editor immediately.

Seems to work the same for me in VSCode, CLion, and nvim. I don't doubt that you have issues with it (I've experienced slow editors & laggy input, it sucks) but I don't think it's inherent to VSCode. Doesn't mean it's not a bug, but if I had that issue I'd try with no extensions to verify, then binary search disabling the extensions I want until I find the one causing the lag.

Re: Claude Code: Now in Beta in Zed

#156

I love Zed and I'm glad you now have native support for Claude. I previously ran it using the instructions in this post: https://benswift.me/blog/2025/07/23/running-claude-code-with... One thing that still suffers is AI autocomplete. While I tried Zed's own solution and supermaven (now part of Cursor), I still find Cursor's AI autocomplete and predictions much more accurate (even pulling up a file via search is more…

I'd also like to second this and probably will in every Zed post. This is the primary reason I'm not ready to switch to Zed just yet.

Re: Claude Code: Now in Beta in Zed

#158
post #142
post #117

Note: if you use SSH-based remote development, this doesn't work. https://x.com/sridca/status/1963271904384401886

That's unfortunate. I use Zed and I'm moving towards containerising my dev environment (using SSH remote dev to connect Zed to the container) because all this agentic stuff seems like a security nightmare. At the very least I want to restrict the blast radius to my repos dir.

I would give them a week or less to support this. They've been improving the debugger so fast, it will take them no time to support remote claude code connections.

Re: Claude Code: Now in Beta in Zed

#159
post #32

Earlier quoted context omitted.

What's so great about zed ?

It uses a fraction of the memory of VS Code and is much faster to launch.

VScode starts very quickly for an electron app. MS did a great job there.

Memory usage of the IDE doesn't matter much when your language servers can eat 10s of gigs of RAM.

Re: Claude Code: Now in Beta in Zed

#160

Earlier quoted context omitted.

What's so great about zed ?

It’s built by the team that built atom which was way better than vscode but was mothballed when Microsoft bought GitHub. They built it from scratch and not on electron bloat so it is a much better foundation. It will take a long time to reach parity with vscode but when it does it will smoke it.

So...nothing.
Post reply on HN