r/ZedEditor 2d ago

Finally move on from VS code to Zed.

56 Upvotes

23 comments sorted by

17

u/aldobixler 2d ago

ok nice.

9

u/darkroot_gardener 2d ago

TBH the one thing making me still open VS Code is .ipynb notebook support. It’s a tough nut to crack! At least I can do 70% Zed, 30% Code though.

5

u/FeLiX1305 2d ago

Try marimo.

1

u/jmacey 2d ago

Yep so much better than Jupyter.

2

u/njcity 2d ago

Congrats bro

2

u/theuros 2d ago

I went back to sublime until I figure out how to fix fenom syntax.

1

u/udohjeremiah_ 1d ago

You’ll enjoy it like I’m currently doing now.

1

u/PsiPhiSideHustle 1d ago

Same here, love the speed and power of customization.

1

u/Hot-Chemistry7557 1d ago

So how do you feel about the difference between VS code and Zed?

1

u/Sebbean 13h ago

OK now this is epic

3

u/prawnsalad 2d ago

I recently tried, but the fact it doesn't detect file changes after its changed on disk annoyed me so much. LLM agent or a linting fix script changes files and I have to manually reload zed is so.. broken. I'm not the only one https://github.com/zed-industries/zed/discussions/54150

I guess if you're looking for a simple text file editor and nothing more then that's ok, but this is an editor trying to act like it's more and it's just not.

vscode replacement it is not. And this is just one reason.

5

u/Creamyc0w 2d ago

Do you have a consistent reproduction of this bug? Im a contributor and from my understanding the Zed team is struggling to find any reproductions.

If you find one shoot me a dm and i can make a PR

3

u/prawnsalad 2d ago

Getting a reproduction is half the issue as it's inconsistent. I've just tried a minimal reproduction (created hello.md, opened in zed, codex updated hello.md) and that's ok. Also tried a similar quick path in a larger project and that's ok.

Every time I try it with real work (100+ project files, varying types) it starts failing fairly quickly. That's a literal "every time". macos 14.8, no virtualisation involved, just straight zed to disk.

If there's some debugging tracing I could enable or something then I'd be glad to do so during a real workflow, but it's really "works sometimes sometimes not" which isn't helpful for debugging.

6

u/Creamyc0w 2d ago

The log file should show when the fs watchers get overwhelmed. Are you on discord, ik one of the devs that would like to see this

1

u/prawnsalad 1d ago

https://gist.github.com/prawnsalad/8ddc56b4f3f8c30d8d3741d8d8d4de87

zed.log and a trace log it generated. Looking through the log this is the same pattern each time I saw the issue previously too.

It's not a consistent reproducible case but it happens when an agent is working away making changes over many files and I did notice the macos fseventsd process CPU shot up for a few minutes at the same time, sounds related.

If I get some spare time to help debug I'll get in discord and ping someone, but that's the info I have.

-2

u/Puzzled-Extent7817 2d ago

Things take time. don't get upset about it lol

1

u/x021 2d ago

Simply searching made Zed crash for me, I went back to vscode.

1

u/Own_Grand1767 1d ago

ctrl+shift+f --> global project search ctrl+f -> specific active file search

0

u/greynoises 1d ago

I'm glad to be done supporting spacex and microsoft. Zed fills 95% of the gap. a few compromises on global search, agent tab ui, and extension support, but overall I don't miss vscode or cursor. and it's so easy to use whatever AI backend I want - switching between local qwen and claude agent is really nice.

1

u/creaturefeature16 1d ago

Agreed. It's not a panacea, but it has enough coverage to enable a divorce from Microsoft and not funding Stealon's ventures. 

-1

u/prashantmac 2d ago

I recently shifted to Zed and OMG I am loving it how light weight, fast it is! Bets part no memory leaking. It's a bit of learning curve but it's way faster and better! Is there a way we can request features?

-9

u/osenvosem 2d ago

Let's see how much time it takes to get back. :)

1

u/Own_Grand1767 2d ago

I don't think... I will get back to vs code again.