Top
Best
New

Posted by salkahfi 15 hours ago

Zed 1.0(zed.dev)
1638 points | 525 commentspage 2
zargon 11 hours ago|
I want to try Zed, but it's just too much of a supply chain attack waiting to happen. https://github.com/zed-industries/zed/issues/12589

I did install it in a VM with virtio-gpu, but it was absurdly slow, so I wasn't able to try it.

skue 1 hour ago||
Had similar concerns, but just noticed they seem to be taking this more seriously now: https://zed.dev/blog/secure-by-default
sev_verso 14 hours ago||
I've been using the editor since the early days and have always been a fan of its visual look and feel, so I was pretty happy to see its UI library open sourced.

I wish GPUI could become the go-to Rust UI library and not just an editor backend.

For that, a couple of changes would be highly desirable: being able to switch the GPU backend from Metal to wgpu (so it could be mixed with vello, for instance), and the ability to integrate into an existing event loop like egui allows you to. If this were easy to do, I would switch from egui in a heartbeat.

combyn8tor 8 hours ago||
They seem to have stopped developing GPUI (or maybe just the public version)?

One of the staff forked it into a community edition https://github.com/gpui-ce/gpui-ce

Does anyone have more details about the state of it?

foresto 12 hours ago|||
> I wish GPUI could become the go-to Rust UI library and not just an editor backend.

In case you find it useful, I recently stumbled upon this project:

https://github.com/longbridge/gpui-component

"UI components for building fantastic desktop applications using GPUI."

bayesnet 11 hours ago||
I took a look at gpui-component a while ago when assessing GPUI for a project I was working on. IANAL but was dissuaded because it's almost certainly not compliant with the Zed license--gpui-component "borrows" gpui code patterns lifted straight from the main zed repo, which therefore must be AGPL/GPL (unlike the gpui-only which is Apache IIRC). Caveat emptor (caveat user?).
airstrike 12 hours ago|||
There's never going to be one GUI library to rule them all, but I find iced the best Rust library at the moment and likely for the foreseeable future.
bayesnet 11 hours ago|||
I'm beating a dead horse here but the challenge is a11y. Chromium wrappers get a11y for free; bespoke UI frameworks must implement accesskit (or something) which is a lot of work and something that (imo sadly) many small teams decide is not worth the investment.
jenadine 13 hours ago||
What's so good about GPUI?
foresto 12 hours ago|||
I haven't used it, but it caught my attention when I read the Text Rendering section of this post:

https://zed.dev/blog/videogame#text-rendering

It looks like their approach could nicely solve a problem that's shared by almost every new GUI toolkit I've tried: text looks terrible, or at least out of place when surrounded by applications built with the desktop's native toolkit.

sev_verso 11 hours ago|||
Clean and polished design, concise Tailwind-style API, and last but not least sustained 120 FPS across complex UI.
exographicskip 13 hours ago||
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

athorax 10 hours ago|
1. I'm pretty sure setting "Maximum Tabs" does what you want, but not positive.

2. Uncheck "Hide .gitignore" setting and it won't do this.

3. Agreed

4. This is configured in the "Restore on Startup" setting (I think you want "Last Session")

tuzemec 9 hours ago||
3. There's "workspace: new center terminal" command that opens terminal as a normal tab.
akho 14 hours ago||
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.)

ideasman42 14 hours ago||
This was reported for Blender/Wayland, they might be able to use a fix like this: https://projects.blender.org/blender/blender/commit/eaf63a35...
Orygin 14 hours ago||
Yes that was the primary issue I had when testing Zed in the past. Keyboard layout not working properly, shortcuts being unusable or un-remappable. Sad to see it's still the case for 1.0
the__alchemist 14 hours ago||
I am posting this because I want to like and use Zed because it's so fast and responsive (Especially on my tablet, which JB turns into a space heater), and has neat functionality like being able to switch to whatever set of hotkeys you use. And I greatly respect the small binary/download size and fast install. From experimenting in Python and rust:

  - Doesn't highlight typos in variable, functions, class/struct names etc. Doesn't highlight rust borrow-check, invalid method etc errors.
  - Doesn't seem to understand either language beyond superficial syntax
  - "Go to definition" (Ctrl + B) Doesn't do anything
  - Doesn't show which versions are valid in Cargo.toml and pyproject.toml
  - No ability to move functions/classes/structs etc to different modules
  - Doesn't seem to understand rust feature gates
  - Doesn't seem to understand what fields a struct has, or params a function has, let a lone what types are valid in them.
  - Rename seems naive

Overall: It is taking a superficial view of the code base, and treating it more as text than a cohesive structure.

edit: Thank you very much for those who have pointed out I needed to disable restricted mode. This has added some introspection and in-line error handling. Some of my concerns are partially-mitigated. It seems when introspection and in-line editing/complete/data appears is inconsistent (But working in many cases), and I do not yet know what rules define this. Refactoring tools like moving are still absent. I will continue to use Zed on my tablet with the LSPs enabled, and observe.

arijun 13 hours ago||
I suspect you may be operating in "Restricted mode," aka it doesn't know if it can trust the directory. In that mode, the main tools like Rust analyzer are quite restricted. All of your complaints should be resolved once Rust Analyzer/basedpyrite are up and running.

I do think they should have a more obvious warning that the current directory is untrusted, right now the little green warning in the corner is way too unobtrusive and will result in many people having the same issue as you.

the__alchemist 13 hours ago||
Nailed it! I will do some more experiments and report back.
wldcordeiro 13 hours ago||
You should edit your original comment since it was user-error not the app being inferior.
the__alchemist 13 hours ago||
Done; ty.
ForceBru 14 hours ago|||
I thought Zed was using tree-sitter: https://zed.dev/blog/syntax-aware-editing? Shouldn't it address all of these issues? Does tree-sitter not understand Python (basically the most popular language out there) and Rust "beyond superficial syntax"? I thought its whole point was that it understands everything about a language's syntax because it builds a concrete syntax tree?
arijun 13 hours ago||
TreeSitter is an amazing tool but is (purposefully) quite limited compared to an IDE--it doesn't even cross file boundaries, so go to definition is a non-starter. Zed uses LSPs like Rust Analyzer to fill that role.
bouh 14 hours ago|||
Did you market the project as trusted? Récent update (à few month) requises the trust to reenable the analyses feature It took me a while to understand lol At Somme point I though that the parker were broken in my codebase xD
the__alchemist 13 hours ago||
I did not. Ty. I will look into doing this.
dmit 14 hours ago|||
> And I greatly respect the small binary/download size

The latest x86_64 Linux build is 136MB. (https://zed.dev/docs/linux#downloading-manually)

As for your list of grievances, they all seem to boil down to the respective LSPs not doing their job? Does Ctrl-Alt-l (lowercase L, not Shift+i) include the language's server in the context menu, and are there any errors reported for it if it does?

the__alchemist 13 hours ago||
Ctrl + alt + l in Zed is not causing any observable effect.
pastel8739 14 hours ago|||
It sounds like LSP isn’t working for you for some reason. Have you installed the extensions for those languages? These things are definitely supported via LSP
TiredOfLife 14 hours ago||
> Overall: It is taking a superficial view of the code base, and treating it more as text than a cohesive structure.

That is the part that makes the space heater

chamomeal 2 hours ago||
Just wanted to mention they added amp jump to helix mode in preview 1.1.2!! Aka "gw" in helix. And it's AMAZING!!! Seems silly but this was the only thing keeping me from fully switching. It's such a snappy editor, and the helix mode is surprisingly faithful. Expand/shrink selection, multiple cursors from searching in a selection, amp jump... it's just amazing.

Helix lovers who are dying waiting for helix plugins, please try this out

scottmessinger 10 hours ago||
I love Zed and have been using it for years. I’ve been especially excited about multi-agent support—it feels like it could be a genuinely powerful model.

That said, the current UX is pretty confusing.

There’s a mismatch in visual hierarchy: selecting an agent in the sidebar appears to change the entire editor’s worktree/branch, but the worktree/branch selector lives in the window titlebar, which strongly implies it controls the whole window. So it’s unclear which is the source of truth—the agent or the window.

That ambiguity shows up in the workflow too. If I want to create a new branch/worktree and then start an agent on it, I can’t do that directly. I have to:

1. create an agent 2. start a conversation (to instantiate it) 3. then switch the branch/worktree

That ordering feels backwards—I’d expect to define the context first, then start the agent.

Even basic navigation is unclear. If I switch the branch in the titlebar, does that affect the current agent, or the whole window? If I want to return to a previous worktree, is that tied to the agent or not? I still don’t have a solid mental model.

It feels like there are two competing concepts:

* agents as independent workspaces * the window as the workspace

Right now they overlap in a way that’s hard to reason about.

The feature has a lot of promise, but the current UX makes it difficult to predict what’s going to happen, which makes it hard to rely on.

DangitBobby 8 hours ago|
I do like the new UI, it beats having a window per workspace, IMO. But personally I'd rather the workspace switcher be based on the project explorer than the conversation history.
kidsil 13 hours ago||
Over the years I’ve tried plenty of fast, "snappy" code editors, but always found myself returning to Sublime.

Zed is the first one that got me to actually migrate. It does a great job of staying out of your way. Search and replace works seamlessly across multiple files with regex, and the extremely fast editing experience feels immediately familiar if you’re coming from Sublime. Being open source also gives confidence in its long-term viability.

Kudos to the team building Zed.

taosx 14 hours ago||
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?

anta40 1 hour ago|
Congtats for reaching 1.0

Gotta say farewell to Sublime. Now Zed is my general purposed text editor. For doing most of my coding work, still use VSCode and nvim.

More comments...