Anyone in our circles using #Zed?
What makes it appealing?
After being a dedicated Vim/Neovim user for over 20 years, I somewhat reluctantly switched to VS Code about five years ago when I started coding in TypeScript, mainly pulled in by its ecosystem. However, I've recently started using #Zed, and I'm incredibly satisfied. One of the biggest reasons I always loved Vim/Neovim was its lightweight and fast performance. Zed feels like it captures the best of both worlds: it's modern and feature-rich like VS Code, yet remains as light and responsive as Vim.
After being a dedicated Vim/Neovim user for over 20 years, I somewhat reluctantly switched to VS Code about five years ago when I started coding in TypeScript, mainly pulled in by its ecosystem. However, I've recently started using #Zed, and I'm incredibly satisfied. One of the biggest reasons I always loved Vim/Neovim was its lightweight and fast performance. Zed feels like it captures the best of both worlds: it's modern and feature-rich like VS Code, yet remains as light and responsive as Vim.
After being a dedicated Vim/Neovim user for over 20 years, I somewhat reluctantly switched to VS Code about five years ago when I started coding in TypeScript, mainly pulled in by its ecosystem. However, I've recently started using #Zed, and I'm incredibly satisfied. One of the biggest reasons I always loved Vim/Neovim was its lightweight and fast performance. Zed feels like it captures the best of both worlds: it's modern and feature-rich like VS Code, yet remains as light and responsive as Vim.
Trying new modal editors to see if anything out there has come close to dethroning the king (vim of course). Helix and Zed were highly recommended options and of the two Helix seems like it could be a contender but Zed? There is no way to close the settings window in Linux and the backspace key doesn't work. Bugs like this are oddly satisfying to find but leads me to believe that these editors aren't being used in real world context or programming environments where building requires the editor getting out of your way. The marketing seems exciting but when put to actual practice you're trapped in the editor. I'm not sure if it's because of the collaboration features or just the fact that writing an editor for most environments is extremely difficult. Could be i'm just so used to vim but :wq has never failed in my history of using it.
The approach seems to be leaving behind legacy and using gpu's for speed which is admirable but I think that's also part of the problem. The reason vim is ubiquitous is because we can type 'vi' on almost any command line, on any platform in any decade and it'll load up. Zed is more of an IDE than an editor and this is where programming style and ideology comes into play. It's an interesting conundrum. What editor you use has in a way always determined what programs you write... Guess it makes sense in that context. #zed #rust #helix #vim #ide
Hold up can we talk about how cute this little file tree icon for KDL files in Zed is?!
Hold up can we talk about how cute this little file tree icon for KDL files in Zed is?!
To the people using #zed for #rust development: Rust (new) module system uses module_name.rs + module_name/ (directory) for organizing modules and sub-modules, so it would make sense to NOT sort directories first in the project panel, so the file and dir for one module are next to each other and not the dir on top and the file elsewhere bellow. How to you configure it to have the natural sorting for #rust project?
Stack Overflow Survey 2025, Developer tools, Category IDE: #emacs isnt even listed 😪 But #vim is on place 5. Even newcomer #zed seems to be more popular than #emacs.
https://survey.stackoverflow.co/2025/technology#most-popular-technologies-dev-envs-prof
i decided to give #zed editor a shot. but cannot find how to enable the behaviour i'm used to in rustrover:
1) automatically select opened file in project tree
2) display dependency sources in project tree
For those of you using #zed , is there a way to tell the project panel to not sort directories first? Especially for rust development it's not convenient to have:
bar/
foo/
bar.rs
foo.rs
where I would like to have:
bar/
bar.rs
foo/
foo.rs