anthony-eid (u/anthony-eid)

anthony-eid commented on The Zed Debugger Is Here zed.dev/blog/debugger... · Posted by u/SupremumLimit

laserbeam · 2 months ago

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!

anthony-eid · 2 months ago

Thank you for the positive energy and I'm glad you liked the under the hood section!

anthony-eid commented on The Zed Debugger Is Here zed.dev/blog/debugger... · Posted by u/SupremumLimit

LoganDark · 2 months ago

Yes. Originally they were Mac-only, then they went open-source and the community added support for Linux and Windows, but AFAICT they've never invested in anything but Mac

anthony-eid · 2 months ago

The core team built Linux support and we're starting to work on Windows as well

anthony-eid commented on The Zed Debugger Is Here zed.dev/blog/debugger... · Posted by u/SupremumLimit

deliriumchn · 2 months ago

they are not intrusive but their entire focus changed on that instead of other features. Entire Git view feels abandoned in half done state yet they spent entire month working on AI chats, AI agents, their own AI edit (that's priced 20 per month yet they boast how light and performant it is -- why isn't it free local model then and why its priced worse than copilot?)

They're moving from "making awesome code editor" into yet another "buy our ai" product

anthony-eid · 2 months ago

We have multiple teams at Zed each with their own focus. In fact, you can see all the projects we're working on if you view our channel notes.

We're going to be adding more features to the debugger for a while

anthony-eid commented on The Zed Debugger Is Here zed.dev/blog/debugger... · Posted by u/SupremumLimit

mort96 · 2 months ago

Is that what Zed's integration does by default?

In any case, what I see most people doing is integrating it with Claude/Copilot/etc. The security concerns specifically obviously don't apply when running it locally.

anthony-eid · 2 months ago

By default Zed has a user choose what type of configuration they want. That could be something like LM Studio, Ollama, or your own API keys to a provider you're already paying for.

AI also isn't shoved in your face when using Zed, there's one small button on the button right.

anthony-eid commented on The Zed Debugger Is Here zed.dev/blog/debugger... · Posted by u/SupremumLimit

nixpulvis · 2 months ago

Is there a tracking issue for watching variables and data breakpoints? I'd like to see that as well.

anthony-eid · 2 months ago

Here's the PR for variable/expression watching: https://github.com/zed-industries/zed/pull/32743

I don't think there's an issue for data breakpoints, but you can make one for us

anthony-eid commented on The Zed Debugger Is Here zed.dev/blog/debugger... · Posted by u/SupremumLimit

laserbeam · 2 months ago

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 would also have liked to see more in the announcement of multiple simultaneous debug sessions, and on how multithreaded debugging is planned. There are really cool things that can be done with multithreaded debugging further down the line that I'd be interesting in hearing about (like how RemedyBG has a DAW-like UI for freezing certain threads, or hitting one button to "solo" a thread and freeze all others).

anthony-eid · 2 months ago

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 just not up to the quality that I and several others expect from Zed, so I didn't advertise it.

There's also a PR for a watching variables/expression that is going to be merged in a couple of days. The functionality is done, but we didn't want to add a feature so close to launch that wasn't fully tested.

Support for data breakpoints will come in the near future. I can't say when because we're planning on focusing on automatic configuration for a while, but it is a priority.

We do support simultaneously debugging multiple sessions at the same time and multithreaded debugging too. There's still more to do with it, but the support is definitely there!