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

191–200 of 343 posts

Re: Zed is our office

#191

Post by piker »

another_twist wrote: post #188

I understand interacting with other engineers right in the editor but I dont get why so many collab tools need to be bolted on to what is basically a text editor. This will only fragment communications since its not just engineers that work in any company. Meaning you'll now have communication spread out in Slack and Zed making collaboration difficult, not easy. I dont honestly dont get the allure of pair programming…

A cynical take is that pair programming in the IDE implies network effects and custom protocols. Just the types of moats necessary to get VC backing.

Re: Zed is our office

#192

Post by girvo »

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…

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

#193

Post by girvo »

tecoholic wrote: post #171
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…

With the AI stuff, it feels like they invested a bit prematurely. When the Agentic editing demo came out (6 months, 10 months ago? It’s a blur), it felt right. Accepting and reviewing edits, live tracking ..etc., felt like pair programming. The ACP addition felt like a natural evolution . With the continuous improvement in CLI tools and people’s experience with them, it feels like doing a live review or edit-by-edit…

The only editor integration I think is semi useful is wiring it into Diagnostics/Problems data that the editor has from extensions. Speeds up the agents flow quite a bit when it leans on that to check its work vs always executing (say) “eslint” directly.

But that can be done easily enough with an MCP extension for your editor/IDE of choice

Re: Zed is our office

#194

Post by eddythompson80 »

another_twist wrote: post #188

I understand interacting with other engineers right in the editor but I dont get why so many collab tools need to be bolted on to what is basically a text editor. This will only fragment communications since its not just engineers that work in any company. Meaning you'll now have communication spread out in Slack and Zed making collaboration difficult, not easy. I dont honestly dont get the allure of pair programming…

My understanding was always that this is a way to monetize a text editor. How else do you monetize dev tools? Developers are used to very high quality free tools. You’re either one of the few old guards (like JetBrains, Microsoft or maybe Oracle) that can sell IDEs and other dev tools because 25 years ago open source dev tools were far from beginner friendly.

But how do you monetize a programming language, a text editor, a build system, a terminal emulator, etc in 2025? The examples are deno, bun, mojo, nextjs, zed, earthly, warp, etc. all know they can’t monetize the actual tool. You monetize services that you build around the tool. Like a cloud/workers/deployment (basically compute), or a sharing service or an AI service, etc. once you have critical mass on your platform, you can find other easy services to offer. Like if Zed has a critical mass of users, maybe the offer “in editor chat”. A small startup with just 3 devs working together can replace slack with zed. Maybe they offer an uptime check service. Why not? Maybe a file sharing service. Maybe a small wiki service, etc. all things that have million other solutions. But if you have critical mass, someone will pay for those things.

Re: Zed is our office

#195

Post by tkfoss »

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.

You just need to channel your inner Akira Nakai. There is no shame in being an artist. Code artisan.

Re: Zed is our office

#196

Post by noobly »

another_twist wrote: post #188

I understand interacting with other engineers right in the editor but I dont get why so many collab tools need to be bolted on to what is basically a text editor. This will only fragment communications since its not just engineers that work in any company. Meaning you'll now have communication spread out in Slack and Zed making collaboration difficult, not easy. I dont honestly dont get the allure of pair programming…

I listened to the founders explain that the current process of syncing up to review or question code is very multi-step and sort of inefficient almost adversarial at a high level. A slack mention, Github discussion, screen share, etc it all ends up being kind of disorganized and painful versus just being able to edit the document collaboratively and directly, perhaps leaving some metadata tagged at certain locations (e.g, notes from a conversation about the code).

It's not like the editor prevents one from still using slack and other external tools, either. I guess I just see the value in in-editor integration to handle that stuff more smoothly, at least for those using the same editor.. I can see myself really appreciating the feature if there's a part of the codebase that consistently trips people up or is under active discussion.

Re: Zed is our office

#197

Post by zie »

recroad wrote: post #176
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…

Agreed. I hear way too much about Zed considering the editor doesn't allow a window to be popped onto a second monitor.

On MacOS 10.15, I have 2 monitors plus the built in on a macbook pro, and I have Zed windows on all 3 of them all the time.

Re: Zed is our office

#198

Post by phcreery »

girvo wrote: post #192
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…

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 :/

This is also a big issue for me and has one of the largets issues for a while. [1] I wish there was font hinting to the like of windows font rendering.

[1] https://github.com/zed-industries/zed/issues/7992

Re: Zed is our office

#199

Post by easygenes »

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…

It says they're targeting Spring 2026 for their 1.0 release, so I'll treat as beta and put a calendar entry in for April 2026 to check back in on it.

Re: Zed is our office

#200

Post by cantalopes »

It's truly showing that the zed team is chauvinistic by dismissing different encodings not being supported and focusing on other things. "It wurks in merica", it gut i guess
Post reply on HN