Live data from Hacker News

Zed is our office

zed.dev

301–310 of 343 posts

Re: Zed is our office

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

[deleted]

Re: Zed is our office

#302

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 dont get why so many collab tools need to be bolted on to what is basically a text editor

It's because the collab tool wants to have access to the code as it changes live. It could and should be done in an editor-agnostic daemon like LSP, but then you wouldn't have editor lock in. And that's why both Zed's collab and VSCode's LiveShare are builtin.

Anyway Zed has a very interesting idea to provide links to codebase places that remain stable even after the codebase changes. This is pretty cool, because so many discussions about code quickly become outdated

Re: Zed is our office

#303

Looks a lot like Google Wave. This is interesting for some things but I don't think coding is it, for the same reason that IntelliJ's CodeWithMe doesn't work for pair programming. And apparently one of the guys is a former Pivot, so it's a little surprising. Pair programming is Two People One Cursor. A critical aspect of it is you're both looking at the same lines of code and working on the same problem and following…

> There's no shared focus.

I never used Zed collab, but isn't there an option to follow someone's cursor rather than having your own separate cursor? Zed even has an option to follow the cursor of an AI agent ffs.

I know that VSCode's Live Share allows you to follow the cursor of someone else. However Live Share is very buggy and will disconnect at times, so it's more like a cool demo than a product.

Re: Zed is our office

#305

Earlier quoted context omitted.

So you rather stay comfortable doing what you were always doing, which is fine but programming is everything but that...

Complexity for the sake of complexity is not a goal everyone should be striving for.

> Complexity for the sake of complexity is not a goal everyone should be striving for.

THIS !

Go's well maintained stdlib just lets me get on with it.

With Rust meanwhile, I have to decide which of thousands of third-party Rust crates is sufficiently en-vogue and well maintained.

Most of my coding work is backend stuff that calls a lot of HTTP APIs, parses a lot of JSON and does a lot of crypto. All that is ready-to-go "out of the box" with Go stdlib and on top of that is faster to get to production in Go than in Rust.

I don't need or want Rust's complexity. As I said I have enough going on at $work...

Re: Zed is our office

#306
What I see in posts like this is that it becomes clear to me that I am not their target demographic.

I work with IDEs and low-code/no-code tools, VSCode is kind of unavoidable in some scenarios as it has become the only programmers editor that some companies bother to provide tooling support for their SDKs, and that is it.

For bettr or worse, everyone and their dog that used Eclipse forks for their SDKs, now is doing VSCode forks.

For historical UNIX purposes vi and Emacs, and then any editor will do when changing some bunch of configuration files, in case nothing else is installed.

In no project I would be able to make Zed our office, that is what stuff like Monday, Jira, Confluene, Trello, Workfront, happens to be.

Re: Zed is our office

#307

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

If software developers use anything other than utf-8 it's on them

Re: Zed is our office

#308

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…

Rust forces you to consider things upfront, or to put it another way, a C developer does what the borrow checker does manually. Sometimes, they do it after asan/ubsan/tsan has reported the issue. Sometimes it's after a segfault. Usually it's after the user hits the bug already. Nix similarly forced issues to be reasoned with upfront.

Yes and most people are happier with a garbage collector than using C, C++ or Rust. There are domains or projects where you have to use one of those languages, but Rust is being used and promoted far outside those niches.

Re: Zed is our office

#309

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

What I remember from those days was saving my work reflexively because the chances of the window manager or text editor crashing at any given moment were quite high. Also, emacs came in for lots of grief for being so slow. Remember “Eight Megs and Constantly Swapping?”

This is not necessarily to endorse Zed; I’m ecstatically happy with my current text editor. However, “we peaked 25-30 years ago” is just not true. Things have gotten better and they continue to do so.

Re: Zed is our office

#310
post #4

I was very surprised to find a "forum" integrated in Zed when I first opened it. But to be honest, it is not something I ever felt the need for and overall I don't like having this in my text editor. So far it never got in my way and that's a good thing, I hope it stays that way :)

yeah, I love Zed - but I turn all this stuff off (even the AI)
Post reply on HN