There are still plenty of things that VSCode does and Zed doesn't. E.g. Dart debugging.
Also there is the VC money problem with Zed, at some point, that money will want returns on every dollar spent.
Also there is the VC money problem with Zed, at some point, that money will want returns on every dollar spent.
So if you have a problem with VC money you should stop using VSCode as well.
Of course they will just invent more accounting terms, like they do with azure, to hide how much money they are losing on it.
https://windowsreport.com/steve-ballmer-calls-bullshit-micro...
2. That's fine, they'll just build some cloud feature
Printf debugging is a usability and productivity disaster compared to an actual debugger.
A developer should use both.
Most of them provide you with a feature list that's a strict superset of printf, because they let you set conditional non-blocking breakpoints that can have side effects. Which is perfect for the situation you've described - logging state without blocking. Then you can block and look through that state + any additional relevant info.
why use so primitive methods that only work under certain circumstances