3 ms·

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

by citbl 9mo ago

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.

koakuma-chan 9mo ago
1. Use println 2. That's fine, they'll just build some cloud feature
- vkou 9mo ago
  > 1. Use println Printf debugging is a usability and productivity disaster compared to an actual debugger.
  - speedgoose 9mo ago
    It depends, it can be useful to easily debug some flows. It’s also sometimes better for interactive applications where pausing the execution would break the interface. A developer should use both.
    - vkou 9mo ago
      They should, but if given the option to only exclusively use one or the other, I would never in a million years pick it. Because I have put in a tiny bit of effort into understanding how to use a debugger. 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.
- tester756 9mo ago
  >1. Use println why use so primitive methods that only work under certain circumstances
Eggpants 9mo ago
I agree that’s Zed is very nice but a ticking enshitiation time bomb. However, you do see how this autocomplete “feature” and its whole copilot everywhere strategy, is about M$’s roi of its ai investment right? 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-microsofts-cloud-revenue/ https://windowsreport.com/steve-ballmer-calls-bullshit-micro...

by citbl 9mo ago

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.

koakuma-chan 9mo ago

1. Use println 2. That's fine, they'll just build some cloud feature

vkou 9mo ago
> 1. Use println Printf debugging is a usability and productivity disaster compared to an actual debugger.
- speedgoose 9mo ago
  It depends, it can be useful to easily debug some flows. It’s also sometimes better for interactive applications where pausing the execution would break the interface. A developer should use both.
  - vkou 9mo ago
    They should, but if given the option to only exclusively use one or the other, I would never in a million years pick it. Because I have put in a tiny bit of effort into understanding how to use a debugger. 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.
tester756 9mo ago
>1. Use println why use so primitive methods that only work under certain circumstances

Eggpants 9mo ago

I agree that’s Zed is very nice but a ticking enshitiation time bomb. However, you do see how this autocomplete “feature” and its whole copilot everywhere strategy, is about M$’s roi of its ai investment right? 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-microsofts-cloud-revenue/ https://windowsreport.com/steve-ballmer-calls-bullshit-micro...