I generally like what Zed is trying to become. However, all of these features and blog posts are frustraing when they struggle to keep basic editor features stable. Edit a file outside of the editor? It's not going to show up in the project pane or the git diff. Need to work inside a container because it's 2025 and we don't need to clutter our local machine with 100s of dependencies and env managers... well now all t…
Curious about the failure to detect FS changes made outside of Zed. Are you on Linux?
Zed is our office
201–210 of 343 posts
Re: Zed is our office
#202Earlier quoted context omitted.
What are you saying here? It is true that VS Code is less bad in terms of responsiveness in comparison to Atom. Zed, however, is written in Rust (i.e., not Electron), and I would guess it is at least an order of magnitude more responsive than VS Code across every possible scenario. Web technologies are an unrivaled technological marvel for what they are, but it is disingenuous to imply they represent anything near th…
It depends. It definitely opens faster and the general UI seems a bit faster, but open a largish file (a few MB) and VSCode will easily out-perform Zed because it doesn't have that fancy CDRT thing. In my experience VSCode is plenty fast. Use it with no extensions and you will have zero problems with performance (though memory use isn't great). The real problems come when you have extensions, especially because it's…
Re: Zed is our office
#203I generally like what Zed is trying to become. However, all of these features and blog posts are frustraing when they struggle to keep basic editor features stable. Edit a file outside of the editor? It's not going to show up in the project pane or the git diff. Need to work inside a container because it's 2025 and we don't need to clutter our local machine with 100s of dependencies and env managers... well now all t…
I know this is silly but the biggest thing that’s driving me away from it is how god awfully blurry it looks on my 1440p screen :/
Re: Zed is our office
#204I generally like what Zed is trying to become. However, all of these features and blog posts are frustraing when they struggle to keep basic editor features stable. Edit a file outside of the editor? It's not going to show up in the project pane or the git diff. Need to work inside a container because it's 2025 and we don't need to clutter our local machine with 100s of dependencies and env managers... well now all t…
I know this is silly but the biggest thing that’s driving me away from it is how god awfully blurry it looks on my 1440p screen :/
Re: Zed is our office
#205Earlier quoted context omitted.
How does Neovim handle outside changes then? Or is there a plugin to make it work? AFAIK it doesn't reload any bufferes when files change. IntelliJ is the only other one I know that does it transparently.
In vanilla neovim you can use autoread... this does depend on a focus event like entering and leaving the pane or switching buffers. However, for my workflow which is "go to a different terminal pane and do some things then switch back" as soon as I focus the buffer it updates. Where as with Zed it'll just keep showing the old content and in fact closing and opening file wont even change what it shows in Zed. It's re…
I use `"autosave": "on_focus_change"` which may be keeping my buffer in sync with the file contents as I switch between terminal and zed.
Re: Zed is our office
#206I generally like what Zed is trying to become. However, all of these features and blog posts are frustraing when they struggle to keep basic editor features stable. Edit a file outside of the editor? It's not going to show up in the project pane or the git diff. Need to work inside a container because it's 2025 and we don't need to clutter our local machine with 100s of dependencies and env managers... well now all t…
I know this is silly but the biggest thing that’s driving me away from it is how god awfully blurry it looks on my 1440p screen :/
Personally, I never registered that as a problem, but I can see the delta in screenshots between versions.
Re: Zed is our office
#207I love Zed. I, mostly, love the direction they are taking the editor in. But. There are now two times I see Zed going in the wrong direction. The AI integration was one. This feels like the wrong direction again. I never really liked the AI integration. It felt off to me. I do love coding with Claude and I think I know why. It presents the "information I need to know" in a way my puny brain can handle it. Colored dif…
Slack revolutionized this for me because I can turn it off anytime I want. When I want focus, I close it and it cannot reach me for some time. Then I pull it up and read all the threads while taking a poop.
Having it in zed is the same: You can just log out of collab anytime you want! You would only use it if you _want_ to use it. When you do want to use it, it's incredible. Someone can just join your channel and work on a tricky problem with you and you don't even need to screen share. It's like the best of discord and slack available at the touch of a button. It's much lighter weight than slack. Slack huddles are super annoying to me. I want it to behave more like discord, and that's what zed does!
Re: Zed is our office
#208Moreover, this would be competing with Google Meet, Teams, Slack, Gather - way too much tech for collaboration
And I wish we were more async-first and less forced to deal with humans, especially over the network.
Re: Zed is our office
#209> Despite attempts to make Atom—an Electron application—more responsive, it never reached the performance standards the team yearned for. This feels like an attempt at deflecting blame. VSCode is another Electron application that ended up having better performance than Atom. There's another Electron adjacent application that has good performance , the one you're probably using right now to read this page. Depending o…
Atom was kinda like emacs. Extensions could do almost anything. VS Code has a limited api that extensions can use