Live data from Hacker News

Zed 1.0

zed.dev

151–160 of 727 posts

Re: Zed 1.0

#151
post #11

Too bad they did not include better search UI into this release. When 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

> Sometimes I just want to have a quick glance at some code and close the search using escape.

How else are you going to have “a quick glance at code” *across* project files without using a new view for that? It sounds like you’re describing something impossible.

Zed’s across files search solves this in a similar way as other tools. Except that in zed you can also edit the code where your search results show up. Zed also has within file search.

Re: Zed 1.0

#152
post #89

I’ve tried it multiple times, but the performance issues on different Macs are too significant to ignore. I appreciate responsive UI, but I also prioritize sufficient battery life.

Interesting because it tripled my mac’s battery life vs cursor

Re: Zed 1.0

#153
Just tried it out and it works great and is really fast! It's a breath of fresh air compared to VS Code. Lots of other editors are fast, but this seems feature complete as well as fast.

Migrating from VS Code was also super simple and integrations with AI assistant seem to just work.

I can definitely appreciate the engineering work that went into it. Loving it so far! Thanks!

Re: Zed 1.0

#154
Been following zed for at least a year now.

Tried switching multiple times from vscode but it's just not feature complete for my use cases. Off top:

- no expanding tabs to fill the window until another one is clicked

- file picker hides .gitignored files

- vertical terminal tabs would be nice

- restart doesn't automatically load the previous window (most recent project)

- while faster/more responsive than vscode on large codebases, still pretty heavy compared to its AI-averse fork, gram; thus I can't use it on the macbook neo

Until some/all of that is improved, it's just uncanny valley territory with no particular killer feature to migrate. Appreciate all the work they've put into it (especially remote ssh parity!) though and like what they're doing in broad strokes

Re: Zed 1.0

#156
post #114

I'd love to see the Alacritty terminal backend swapped out with libghostty (or more likely libghostty-rs). The work Mitchell is doing with Ghostty and the approach Zed has taken seem super aligned. And Mitchell definitely seems to want to make Alacritty an easy target for conversion, he was just talking about being open to help support Warp with it: https://x.com/mitchellh/status/2049159764261925005

What is Ghostty's advantage over Alacritty?

Re: Zed 1.0

#157
Great product! Would love to see some search (tree view) and git (staged vs unstaged diffs) improvements in the future!

Re: Zed 1.0

#158
post #130

Here is a top-level comment for people who want to post the things they wish Zed had. Request: please be sincere if you claim "the one thing that keeps me from using Zed is X" ... because let's face it, there is probably more than one thing. Editor ecosystems are complex beasts, and it is ok if people are slow to switch, but the "one thing" claims are rarely credible to me. Anyhow, such comments are rarely consistent…

I wish Zed had built-in APIs for extension developers to allow for more customizable text transformations. In particular, I want to write tools that have more control over what a buffer displays. Imagine a Markdown extension that gives Zed something close to the WYSIWG experience of Obsidian. To make this happen, I think something like a customizable presentation layer to transform the buffer's contents and adjust cursor movement would be a great start. Vim has a 'conceal' feature that could serve as an inspiration or reference point. [1]

I have no affiliation with Zed, though I have applied to work there, so I'm hardly neutral. I've been an enthusiastic user for probably two years. I don't expect perfect alignment with what I want, and sometimes the team doesn't respond how I would like with particular issues. But man, in a pretty suboptimal world right now, Zed is an amazing thing to have: open source, regular updates, extensions, nice settings. In the past I've used BBEdit, Eclipse, TextEdit, Sublime, Emacs, VS Code, Jetbrains, Helix. Zed is my favorite by far, probably because of the latency. It is an intangible feeling that just clicked immediately for me.

Personally, as a mostly independent developer/researcher, I go through bursts of re-evaluating my tools. To give some context about my newer tools over the last few years: Ghostty, Nushell, Podman, Nix, Mochi, Monodraw, Swish (window manager for macOS), Base (macOS SQLite editor by Menial), LM Studio, (probably obviously) Claude Code. So for a "seasoned" developer, I'm probably more open to new tools than most? Oh, totally off-topic but I think some of the lesser appreciated new open source tools / formats / conventions are: KDL (https://kdl.dev), Typst, and (evaluating) Djot, Cocogitto (Conventional Commits, took me long enough).

[1] https://alok.github.io/2018/04/26/using-vim-s-conceal-to-mak...

Re: Zed 1.0

#159
post #125
post #114

I'd love to see the Alacritty terminal backend swapped out with libghostty (or more likely libghostty-rs). The work Mitchell is doing with Ghostty and the approach Zed has taken seem super aligned. And Mitchell definitely seems to want to make Alacritty an easy target for conversion, he was just talking about being open to help support Warp with it: https://x.com/mitchellh/status/2049159764261925005

Looks like Mitchell said he's already on it https://x.com/mitchellh/status/2049514540505964549

He gave me a quick response, should have checked back before posting here

Re: Zed 1.0

#160
post #44

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 wit…

Had the same experience with a rails project, it injected an LSP+linter we don't use in our project and it has really annoying to figure out how to disable it in a settings. Having to debug an editor's settings JSON the first time you use it is not a good UX, it should be optional to enable it instead of assuming we want aggressive on-save linting/autoformatting (that the repo doesn't even have configuration files).
Post reply on HN