I don't understand why text editors became so complicated. When I ran zed, I think my gpu wasn't properly used and it ran at 5 fps. I couldn't even get the thing to boot..
Remember when people had 1024x768 and coded perfectly fine software without instant messaging pinging every few minutes? We peaked there
Zed is our office
281–290 of 343 posts
Re: Zed is our office
#282Earlier quoted context omitted.
…you’re free to use other editors? People like Zed. They like IntelliJ. They like VSCode. If you have an aesthetic preference against all professionally maintained IDEs, I think you’re in the minority.
...doesn't mean the majority is right :)
That reminds me of a French saying that seems fitting:
C'est pas parce qu'ils sont nombreux à avoir tort qu'ils ont raison!
Re: Zed is our office
#283Random thing spotted in the article:
> "Wish there was a windows laptop I could buy that is good"
What does it even mean? There are macs, there are chromebooks and there are just laptops. Wth is a Windows laptop? There's a good Linux laptop?
Just a nit :P
Re: Zed is our office
#284Maybe I'm old, jaded, stubborn and paranoid, but something about a coding editor that is controlled by a company is off-putting to me. It's even more off-putting when you add Zoom, Slack and everything else into said editor.
"Collaboration as it stands today is considered alpha, and for the time being, is free for all to use!"
This doesn't fill me with confidence.
Re: Zed is our office
#285I 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 :/
I have the same problem on Linux-wayland/4K screen. I can't get it to look anywhere near "okay".
Re: Zed is our office
#286I 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 :/
It's been that way since day one. Wild that they haven't fixed it. Edit: it was fixed in Oct 2025, version 0.207.4
Re: Zed is our office
#287I 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…
> 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... “Can I tell you about our lord and saviour Nix?” Kidding, but seriously though I’ve found having to work in a container to be a bit clumsy, even with good tooling around it. As you said it’s 2025, and there are other ways to have reproducible toolchains that don’t pollute th…
> “Can I tell you about our lord and saviour Nix?”
The "just use Nix" people are just like the "write it in Rust" brigade.
And the things both groups promote share exactly the same problem ...
A stupidly enormous learning curve.
That's why your average person prefers to just the job done in a container vs Nix, or in Go vs Rust.
I'm sure Nix is awesome, just like I'm sure Rust is awesome. But honestly, I've got enough going on in my brain at $work and $home without having to wrangle some obscure config syntax (Nix) or obscure low-level language complexities (e.g. Rust's infamous borrow-checker).
Every time I go back and look at Rust or Nix my brain is just like .... no, thanks.
Re: Zed is our office
#288Earlier quoted context omitted.
My understanding is that he is involved in the development of Zed I find Zed's feature choices to be really poor, and then I probably made a poor association based on his talking about zed
Hashimoto writes Ghostty in the Zig programming language. There might be a mixup here between Zig and Zed.
Yeah, they're not zigging, they're zagging, er, zedding...
Re: Zed is our office
#289Earlier quoted context omitted.
We need more selinux and sandbox-exec in daily dev lives. There's no reason to bring a whole new system along just to restrict some access.
Any references to how you use selinux? I've used bwrap and firejail, but I don't feel confident that I'm not leaving holes open?
Honestly - no. To use selinux you need to commit to actually learning how it works and experimenting a bit. I don't think there's an easier way than reading both redhat (https://docs.redhat.com/en/documentation/red_hat_enterprise_...) and NSA (https://www.nsa.gov/portals/75/documents/resources/everyone/...) docs.
If you're happy with firejail, make sure you use whitelists only and you'll be 90% there with what's possible to achieve.
Re: Zed is our office
#290Earlier quoted context omitted.
Often projects need a history of stable checkpoints, and source control is one way to provide that.
Yes, but does it need all the ceremony surrounding it? If, every time I saved the file, the changes were analyzed and committed to git, and a useful commit message included, and commits squashed automatically and pushed and tested and tagged (using magic, let's say); if the system existed in the background, seamlessly, how would our interactions with source control and with other developers look?
> if the system existed in the background, seamlessly, how would our interactions with source control and with other developers look?
They would look like noise.
You would be the source of that noise.
One commit per edit? Nonsense.
Me and any other developer would hate to share a repository with you.