Live data from Hacker News

The Zed Debugger Is Here

zed.dev

191–200 of 211 posts

Re: The Zed Debugger Is Here

#191
post #36

It's a niche feature, but what's keeping me from switching yet is that they zed doesn't support ctrl+scroll to zoom/change font size yet. Because I am accustomed to a non-US keyboard layout that doesn't make the regular key bindings for changing zoom easy, I got too used to doing it this way. It's honestly looking to be a great modern IDE with almost everything I'm wishing for.

May I ask which layout is that? On most that I have encountered (using hr daily), + and - don't require modifiers.

It's a swiss french layout and the problem is mainly +. But it's also that + and - are quite far apart so the mouse wheel is just easier.

Re: The Zed Debugger Is Here

#192
post #166

Earlier quoted context omitted.

I'm not interested in using text editors with chat bot integration, hope this clarifies things

So you're just here to be an AI curmudgeon with no valuable input to the debugger conversation topic whatsoever, with no experience with Zed and no intent to ever even try it? Thanks for all the relevant and useful hot takes I guess.

The way I see it, I shared thoughts on Zed, as someone who was once really interested in Zed and once tried to switch to it, in a discussion about Zed. It's not about the Zed debugger, but it's not like this thread is lacking in discussion of the debugger.

Am I an AI curmudgeon? I wouldn't necessarily use that word, but it's not entirely inaccurate.

Re: The Zed Debugger Is Here

#193
post #167

Earlier quoted context omitted.

I just tried it out again. It seems like you can disable the chat bot integration by adding this to the config: "agent": { "enabled": false } However from the documentation[1] I can't see a way to disable the "AI" predictions button (which asks you to sign in to their online "AI" service with your GitHub account). Am I missing something? [1] https://zed.dev/docs/configuring-zed#edit-predictions

Setting this to none should remove that button. "features": { "edit_prediction_provider": "none" }

Really? That's not mentioned in the documentation, it seems like the whole "features" object is missing. Thanks anyway.

Re: The Zed Debugger Is Here

#194

Zed feels like what Lapce, Helix and Neovim couldn't achieve in the time they spent. I started using Helix back around 2021-2022 and just couldn't get over the bugs and lack of integration. It was good, but PHP support (I was working at an older company) was bad. Neovim felt closest to a nice editor but there were some popular community-driven plugins that were very stubborn, and alternatives were just very slow. I w…

This might be off-topic, but I really want to use Helix. I've been using Vim keybindings for a few years now but it's so unintuitive, there's still so many things I can't do efficiently in Vim. Helix just makes so much more sense for my brain. But I don't use Vim/Neovim by itself, I always use an integration with an editor like VSCode or Obsidian (Obsidian's Vim emulation isn't great, but it's good enough). Helix just isn't there yet with VSCode or Obsidian.

I wish more "Vim successors" would focus more on integrating with existing IDEs, rather than becoming one themselves. I don't want to have to set up an entirely new workflow when I change how I edit text.

That's also why I haven't tried using Neovim as a standalone IDE. It looks like I'd really like it, but I don't want to be locked in to using Vim.

Re: The Zed Debugger Is Here

#195

Earlier quoted context omitted.

I used to use separate of each, but switched to the ones integrated into Zed. being able to click on a file in one and have it open one frame later in the others is very productive for me. e.g. click a link in my test runner's output to a line in a file and immediately jump to that file in the file tree and that line in a buffer.

Hmm, open tab performance hasn't been a concern of mine... since the turn of the century? (cough) Not using electron of course. I suspect a preference here has more to do with how many monitors one has. I have multiple so prefer multiple windows. If away from my desk, having a fullscreen window split makes sense.

Yeah, in my office I use a single ultrawide. And I'm often programming away from a desk on a laptop.

Back in the day I had a multi-monitor setup and that was super nice with a tiling VM and a terminal/*nix based development environment.

Re: The Zed Debugger Is Here

#196

Earlier quoted context omitted.

There's a pair of config settings to turn off all of the AI features: features.edit_prediction_provider=none agent.enabled=false There's additional config to set if inline assistance is automatic, only when the user presses a key, fully disabled, etc.

I’d prefer an option at first start perhaps, to turn it on.

That might be how it works, I haven't been through the new user flow in a while.

Re: The Zed Debugger Is Here

#197
post #77

Earlier quoted context omitted.

Nothing has been able to replace Magit for me, yet. Having a Zed UI for Git like Magit is my dream feature request. With that said, Zed has effectively replaced all of Emacs for me, besides Magit. Additionally, typing in other editors feels noticeably higher latency than Zed :) I've been daily driving Zed for almost a year now -- works best on TypeScript, Rust, and Go projects, in my opinion. There's just so much fun…

Zed reminds of the days when Atom was big. It was a good time, but it always left me wondering how long it would last as it leaned heavily on community support for nearly everything useful outside a few packages Such a situation makes me worry about it keeping up if popularity wanes. With JetBrains for example at least I know that paying for the editor it will keep getting proper updates and support even if it isn’t…

And Sublime, BBEdit, TextMate, Notepad++, Ultraedit, Slick, vi, vim, XEmacs, Emacs, nano, joe, jEdit,....

Re: The Zed Debugger Is Here

#198

Zed feels like what Lapce, Helix and Neovim couldn't achieve in the time they spent. I started using Helix back around 2021-2022 and just couldn't get over the bugs and lack of integration. It was good, but PHP support (I was working at an older company) was bad. Neovim felt closest to a nice editor but there were some popular community-driven plugins that were very stubborn, and alternatives were just very slow. I w…

> PHP support (I was working at an older company) Not sure why PHP needs a qualifier like this.

People keep forgetting the UNIX tools they love sooo much predate PHP, follow the same worse is better mentally, and trace back to 1969, but for some strange time travel reason, they are considered modern.

Re: The Zed Debugger Is Here

#199

Zed is what real product development looks like. So nice to have an option that doesn’t repackage the whole damn chromium engine (again)

I like some of their choices, but I wouldn't say that releasing your product for a minority operating system only, then following up with yet another minority operating system much later, then stuffing AI features in there when you don't even have debugger support... The list goes on; one man's "real product development" is another's list of mistakes.

They got the baseline feature set right, IMO, but probably could've spent some more time looking at the actual, real demographics of development (and who is most likely to appreciate performance as a feature and share those ideals).

Re: The Zed Debugger Is Here

#200

I'm very happy to see work on the debugger. This is the main feature preventing me from switching full time to zed. Unfortunately, "here" is not accurate. Not having a watch window, a stack trace view, and no mention of data breakpoints in the announcement still keeps the "beta" tag. I know those features will arrive eventually, but what is described is definitely not sufficient for 97% of my debugging sessions. I wo…

Hey Laserbeam, I'm one of the devs that made the debugger and the one that wrote the article. We do have a basic stack trace view that basically all debuggers support. What's coming out in the near future is a stack trace view in our multi buffer system. In fact, you can use the "show stack trace" action while in an active debug session to expand the call stack in a multi buffer, where each excerpt is a frame. It's j…

I am VERY confident you guys have everything I mentioned either half working or coming shortly, so I'm not worried. I just saw a "the debugger is here!" announcement, then read the announcement, and saw what's still under todo... My reaction is "well, it's not here, it'll be here in a few weeks". And that's ok ^.^

Am impressed by the under-the-hood discussion though. Keep up the great work!

Post reply on HN