Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Zed is our office

zed.dev

Post reply on HN
Print view View original

331–340 of 343 posts

Re: Zed is our office

#331

Post by marssaxman »

girvo wrote: post #328
marssaxman wrote: post #318

Earlier quoted context omitted.

Thank you for the example. That shows exactly what I was talking about, so this issue is clearly (at least somewhat) a matter of taste. To my eyes, those VSCode samples look harsh, crudely pixelated like something out of the 1990s, while the Zed samples look like normal anti-aliased text.

No other editor or app that I use on macOS looks like this. None. This is not just AA, I like properly AA’d text.

Ahh, thanks for the explanation. I guess I was thrown off by the screenshot attached to that bug report upthread, where someone compared zed's rendering against completely non-anti-aliased text rendered by VS Code.

Re: Zed is our office

#332

Post by chanux »

verdverm wrote: post #114
pprotas wrote: post #104

Earlier quoted context omitted.

I removed the collaboration panel from my bottom bar and don’t have to deal with it at all. Can recommend

I stay away from anything Hashimoto is making after my experiences with TF & HCL, or at least the bar is much higher / projects get a lot more scrutiny

Care to elaborate on Terraform/HCL issues?

I have worked quite heavily with Terraform and went through the trough of despair myself. But after a while I realized

1. It does quite a good job at what it does, given the complexity it's handling for us.

2. We have been expecting more and more from the tool.

Mitchell himself called Terraform stuck in the past in some social media platform. However, I don't see Terraform sucking up all the interest and cash in infra, making the landscape barren so nothing else can grow. So, I hope something better will pop up. Until then, Terraform is good for what it does.

Re: Zed is our office

#333

Post by Shorel »

fragmede wrote: post #327
Shorel wrote: post #290

Earlier quoted context omitted.

> 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.

ye gods, have you never heard the word squash?

Why should I do your work instead of mine?

Even your comment is also noise =)

Re: Zed is our office

#334

Post by aiiizzz »

While certainly an amicable goal, I doubt that many companies/groups would be willing to put their comms inside zed, where it feels locked outside any other ecosystem.

Re: Zed is our office

#335

Post by rounce »

traceroute66 wrote: post #287
rounce wrote: post #225

Earlier quoted context omitted.

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

I didn’t say “just use Nix”, I jokingly made a reference to street evangelists and the similarities they have in their approach with people who are excited about a particular technology. In fact I said “Nix or otherwise” implying there are many options when it comes to reproducible per-project environments.

Re: Zed is our office

#336

Post by brabel »

giancarlostoro wrote: post #312
brabel wrote: post #300

Earlier quoted context omitted.

Theres a plugin for Claude Code and you can use Claude models from Copilot in IntelliJ. Are those options worse than Zed, especially considering other comments about Zed missing basic editor stuff?

Claude Code in IntelliJ just opens a terminal tab. Claude Code in Zed feels integrated into the editor as if it were a natively supported model.

The copilot plugin with Claude models (Sonnet models) is very integrated in the IDE, and so is Jetbrains AI (even more integrated than Copilot) which I believe can also use those models. So I wonder what's the actual difference.

Re: Zed is our office

#337

Post by verdverm »

rounce wrote: post #335
traceroute66 wrote: post #287

Earlier quoted context omitted.

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

I didn’t say “just use Nix”, I jokingly made a reference to street evangelists and the similarities they have in their approach with people who are excited about a particular technology. In fact I said “Nix or otherwise” implying there are many options when it comes to reproducible per-project environments.

joking or not, people are very tired of the evangelists (fanbois?) from these ecosystems, and this culture around them is one reason others stay away. The broader trend is developers are burnt out on tooling churn

Re: Zed is our office

#338

Post by verdverm »

nixpulvis wrote: post #57
wateralien wrote: post #6

Zed is lovely and I hope it becomes super successful but this kind of mass collaboration might be ok for meeting minutes... maybe. But thinking of it for coding it gives me shingles. Code by mass live committee. Yikes.

Pair programming can be really great. Or horrible. Depends entirely on the people. This would be good for code-walks too though. Instead of having to share your screen and hope the video comes through well. Everyone can follow along in the comfort of their own editor.

re: pair programming, the lion's share is moving to be with agents, not humans.

I think the fundamental flaw that dooms this feature is non-developers. Do teams and orgs want more than one chat system? I suspect not. It will be very hard (impossible) to convince people who can pay back the VCs to switch zed as the basis for their chat for all employees.

> video comes through well

I cannot recall the last time resolution or latency was an issue (zoom/meet)

> Everyone can follow along in the comfort of their own editor.

With different screen resolutions, you cannot be sure everyone sees the same code. Video guarantees this

Re: Zed is our office

#339

Post by fragmede »

Shorel wrote: post #333
fragmede wrote: post #327

Earlier quoted context omitted.

ye gods, have you never heard the word squash?

Why should I do your work instead of mine? Even your comment is also noise =)

Who's asking you to do my work instead of yours in this hypothetical magic future system that I've invented in my head?

Re: Zed is our office

#340

Post by gonational »

BinaryPie wrote: post #102

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…

This, 100%.

So many of the basic features (e.g., automatic Python venv, Pyright running, etc.) have random bugs that pop up from time to time, making the basic editor unreliable.

My fear is, if they keep going in this direction (adding bloat without fixing basic functionality), they'll be a perfect fit for Microsoft acquisition, at which point I'll have to switch careers, because there isn't any other editor out there that I like.

Post reply on HN