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

221–230 of 343 posts

Re: Zed is our office

#221

Post by verdverm »

gherkinnn wrote: post #216
echelon wrote: post #145

Earlier quoted context omitted.

This feels like a huge distraction from building an IDE. A monnumentous yak shave. I've never used or cared for multiplayer in VSCode or JetBrains. It's silly. I've never been the pair programmer type. The only time I've needed to share an IDE is during a SEV or ridiculously complicated systems bug, and that's 1% of the time.

So you're saying that you're not the target audience, therefore it is silly?

people can abstract and reason about issues like...

1. Until this is possible without lock-in to a specific IDE, it's going to be heavily gated by adoption and network effect.

2. What are you going to do about communication with non-devs who don't use any IDE? Do I now have multiple chat tools I need to give attention to?

3. Bringing the attention economy to our primary work tool is probably a bad idea in the long run, given the evidence we have more broadly about the impact of the attention economy

4. They are also proposing a new version control database, which makes adoption and interoperability an even harder task. https://zed.dev/blog/sequoia-backs-zed#introducing-deltadb-o...

5. We are in an AI hype cycle, which comes with a lot of experiments and baggage. We're seeing both fandom and rational pushback against this experiment (and others)

Re: Zed is our office

#222

Post by verdverm »

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

sorry and thank you, I stand corrected in several comments about my missassociation based on a blog post Hashimoto did for Zed

Re: Zed is our office

#223

Post by fragmede »

apsurd wrote: post #72
fragmede wrote: post #41

Earlier quoted context omitted.

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?

automated commit message will tell you the "what" not the "why". In any circle of "what makes a good commit message and why even do it" discussions, invariably the recommendation is to explain the "why" and leave out the self-evident "what". If your stance is that commit and commit messages can be automated away then we might as well not even have them. I don't share this view, but yeah in this world we don't need AI…

> we might as well not even have them.

You can't see any value in being able to see the "what" in a short bit of English at a glance vs having to analyze a 300+ line diff to figure out what it's doing?

Re: Zed is our office

#224

Post by twelvedogs »

NewsaHackO wrote: post #204
girvo wrote: post #192

Earlier quoted context omitted.

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 don't have this problem, but issues like this are always a huge barrier, especially when you want users from a polished code editor like VSCode. Personally, I use it because VSCodium does not support the default Python LSP on my Linux box. I like it, but there are definitely areas that seem rough around the edges. My biggest issue is the size of the font and icons. I use a 4K screen, and while the font is readable,…

Yeah same, plus I have poor eyesight so I have to zoom then to click anything

Re: Zed is our office

#225

Post by rounce »

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…

> 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 the rest of your system environment Nix or otherwise.

Re: Zed is our office

#226

Post by patcon »

verdverm wrote: post #96

I really really don't want comms or multiplayer tools in my IDE. Don't bring the attention economy to my cave of solitude, it's where I go to escape all that noise

This is a strong divider between types of minds. I respect your type, but know that others exist and they want these things. It's not crazy, it's just another way.

Re: Zed is our office

#227

Post by recroad »

zie wrote: post #197
recroad wrote: post #176

Earlier quoted context omitted.

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.

You have to open three Zed instances, don't you?

Re: Zed is our office

#230

Post by adastra22 »

rounce wrote: post #225
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…

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

In the case of AI tools it is for security reasons, not just reproducible toolchains.
Post reply on HN