Live data from Hacker News

Zed: High-performance AI Code Editor

zed.dev

281–290 of 447 posts

Re: Zed: High-performance AI Code Editor

#281
post #232

Earlier quoted context omitted.

Zed employee here - there are no limits if you bring your own API keys!

Awesome, thank you. I've been trying it for the last few minutes, really liking it. Pretty impressed with how well it works using ollama + qwen3:32b Two nitpicks: 1) the terminal is not picking up my regular terminal font, which messes up the symbols for my zsh prompt (is there a way to fix this?) 2) the model, even though it's suggesting very good edits, and gives very precise instructions with links to the exact pl…

1. You can specify your terminal font via terminal.font_family in zed settings.json

2. Not sure.

3. For most languages, the default is to use prettier for formatting. You can disable `format_on_save` globally, per-language and per project depending on your needs. If you ever need to save without triggering format ("workspace: save without formatting").

Prettier is /opinionated/ -- and its default is `singleQuote` = false which can be quite jarring if unexpected. Prettier will look for and respect various configuration files (.prettierrc, .editorconfig, via package.json, etc) so projects can set their own defaults (e.g. `singleQuote = true`). Zed can also be configured to further override prettier config zed settings, but I usually find that's more trouble than it's worth.

If you have another formatter you prefer (a language server or an external cli that will format files piped to stdin) you can easily have zed use those instead. Note, you can always manually reformat with `editor: format` and leave `format_on_save` off by default if that's more your code style.

- https://zed.dev/docs/configuring-zed#terminal-font-family

- https://zed.dev/docs/configuring-zed#format-on-save

- https://prettier.io/docs/configuration

- https://zed.dev/docs/languages/yaml#prettier-formatting

- https://zed.dev/docs/configuring-zed#formatter

Re: Zed: High-performance AI Code Editor

#282

I really want to move off VS Code and start using Zed, but unfortunately the text is always extremely blurry. It's just unusable. I check back on the GitHub issue every few months and it just has more votes and more supportive comments, but no acknowledgement. Hopefully someone can rescue us from the sluggish VS Code. https://github.com/zed-industries/zed/issues/7992 I have a 1440p monitor and seeing this issue.

Thank you, I bring this up in every Zed thread on the internet, hopefully the devs will eventually fix it. Until they do, Zed is simply unusable on regular-DPI displays, at least in light mode. See these screenshots: Example Zed screenshot, using "Ayu Light": https://i.ibb.co/Nr8SjvR/Screenshot-from-2024-07-28-13-11-10... Same code in VS Code: https://i.ibb.co/YZfPXvZ/Screenshot-from-2024-07-28-13-13-41...

I don't see the difference except that the font is thinner in the Zed screenshot. Try with same font weight and color scheme.

Re: Zed: High-performance AI Code Editor

#283

I really want to move off VS Code and start using Zed, but unfortunately the text is always extremely blurry. It's just unusable. I check back on the GitHub issue every few months and it just has more votes and more supportive comments, but no acknowledgement. Hopefully someone can rescue us from the sluggish VS Code. https://github.com/zed-industries/zed/issues/7992 I have a 1440p monitor and seeing this issue.

Several replies saying that the issue is with the monitor. When the issue has an example showing Zed next to VS Code, and you can see that Zed is much blurrier: https://github.com/zed-industries/zed/assets/5507503/9883d38...

Looks like you're trying to turn off antialiasing entirely, which is a bit niche

Re: Zed: High-performance AI Code Editor

#284

I'm sure it's fast, but is it accessible? Am I as a screen reader user going to get fired if the company I work at decides one day to have all of their devs use this? And if not, any plans to make it so? Might sound a little brusque but this really is the stakes we're playing with these days.

They can pry my vt220-based editor from my cold dead hands.

Re: Zed: High-performance AI Code Editor

#285
post #22

Meanwhile I'm checking Helix editor every 6 month to see if authors became any less hostile to the idea of thinking about considering of starting thinking about potentially adding copilot support. https://github.com/helix-editor/helix/discussions/4037

The authors don’t seem hostile at all. They’re firmly against putting work into a feature they don’t care for but welcome pro-AI users to make it happen. For some reason the latter group hasn’t seemed to accomplish it.

Re: Zed: High-performance AI Code Editor

#286

How does Zed fare for C++ development? Last I checked it did not support CMake as a build system.

You can set up tasks to run cmake for you: https://zed.dev/docs/tasks

Personally, I just use the terminal for my build tools and Zed talks to clangd just fine for autocomplete etc.

Re: Zed: High-performance AI Code Editor

#287

I generally use Neovim, but Zed was the first code editor that made me go, "Wow, I can see myself actually using this." My only gripe is the "Sign In" button at the top that I can't seem to remove. But apropos TFA, it's nice to see that telemetry is opt-in, not opt-out.

Yeah. I've been using vim since the 90's. A bit of emacs here and there, and more recently some helix too. Zed was the first GUI editor that took me over. I've always hated VSCode, but Zed is so fast and its UI just clicks on me that I've been using it as my main editor for months now.

Subscribed to their paid plan just to keep the lights on and hoping it will get even better in the future.

Re: Zed: High-performance AI Code Editor

#288

Earlier quoted context omitted.

Zed employee here - that sounds like a bug, sorry about that! If you're okay sharing the conversation with us, would you mind pressing the thumbs-down button at the bottom of the thread so that we can see what input led to the 400? (We can't see the contents of the thread unless you opt into sharing it with the thumbs-down button.)

No problem, and thanks for the response here! I sent two feedback threads (added a second test where a file succeeded to edit and the rest failed). It was actually quite entertaining seeing the model try troubleshoot stuff anyway. I used github copilot's sonnet 3.7. I now tried copilot's sonnet 3.5 and it seems to work, so it was prob a 3.7 issue? It did not let me try zed's sonnets, so I don't know if there is a pro…

Thanks for the information. We can reproduce this using Copilot Chat. We're fixing now. We'll let you know when the fix is out.

Re: Zed: High-performance AI Code Editor

#289

I tried Zed out and successfully got Claude chat working with my API key. But I'm not sure how to get predictions working. When the predictions on-ramp window popped up asking if I wanted to enable it, I clicked yes and then it prompted me to sign in to Github. Upon approving the request on Github, an error popover over the prediction menubar item at the bottom said "entity not found" or something. Not sure if that's…

I was trying to figure this out too. It seems like you need to sign up for their "Zed Pro" subscription for it to work at all, and nothing indicates this anywhere. It just appears broken. Not the best first impression.

[deleted]

Re: Zed: High-performance AI Code Editor

#290

It's honestly frustrating to see such a promising product make _so many_ sub-par product decisions. It's probably one of the only products that I have genuinely tried using > 5 times and gave up right after. I would grant this if they were new in the block, but it's been a while now. If they had focused on 1. Feature-parity with the top 10 VSCode extensions (for the most common beaten path — vim keybindings, popular…

Huh? I'm a bit confused by your comment:

1. Zed has been working great for me for ~1.5 years while I ignored its AI features (I only started using Zed's AI features in the past 2 weeks). Vim keybindings are better IMHO than every other non-vim editor and the LSP's I've used (typescript, clangd, gleam) have worked perfectly.

2. The edit prediction feature is almost there. I do still prefer Cursor for this, but its not so far ahead that I feel like I want to use Cursor and personally I find Zed to be a much more pleasant editor to use than vscode.

3. When you switch the agent panel from "write" to "ask" mode, its basically that, no?

I'm not into vide coding at all, I think AI code is still 90% trash, but I do find it useful for certain tasks, repetitive edits, and boilerplate, or just for generating a first pass at a React UI while I do the logic. For this, Zed's agent feature has worked very well and I quite like the "follow mode" as a way to see what the AI is changing so I can build a better mental model of the changes I'm about to review.

I do wish there was a bit more focus on some core editor features: ligatures still don't fully work on Linux; why can't I pop the agent panel (or any other panel for that matter) into the center editor region, or have more than one panel docked side by side on one of the screen sides? But overall, I largely have the opposite opinion and experience from you. Most of my complaints from last year have been solved (various vim compatibility things), or are in progress (debugger support is on the way).

Post reply on HN