[peoplefromibiza]

it is actually faster and snappier to use on a beefy M2 max, on the same hardware zed starts up in half the time. the difference is very noticeable. of course it is much less configurable and doesn't work with a lot of things VS Code can do easily.

edit: see this comment for a much better explanation than mine of what I originally meant https://news.ycombinator.com/item?id=39409763

[ncruces]

Startup would have to be terrible for me to bother.

VS Code starts in under a couple of seconds, and I have it open all day long; once open, other windows open even faster than that.

If it took any longer than a couple of seconds, I'd start blaming the extensions other editors won't have.

[peoplefromibiza]

> Startup would have to be terrible for me to bother.

that's just the first noticeable difference.

but there have been instances lately where opening, editing and saving the file took me less time with zed than just open it in VS Code and waiting for it to be ready for inputs

> VS Code starts in under a couple of seconds

I am talking about relative speed differences. Imagine you open the same code base and the editor is ready in half a second. going back to the "slower" one would be unbearable.

now admittedly zed is no way near to the extensibility of VS Code so it is probably doing less and that's where probably much of the speed difference comes from, but it can't really be overlooked once you experienced it.

[cmiller1]

In a perfect world startup times would be indistinguishable from instantaneous.

[ncruces]

And for an image previewer I'd care.

If I'm opening a codebase with thousands of files, I don't mind to wait a couple of seconds, as long as it's responsive afterwards.