VSCodium starts up faster for me than Zed which I compiled yesterday with release mode. Here I am referring to the time spent just on waiting for the window to start up, not the extensions and all that I am using with VSCodium, that takes time. I wonder why this is, that VSCodium shows the window quicker than Zed.
Regardless, I will give Zed a try with Go development. I assume Zed has extensions, too? Are there any extensions for Go? If so, I might replace VSCodium with Zed but only if it has similar features to VSCodium. If not, I will stick to VSCodium as there is no reason for me to change.
They built it from scratch and not on electron bloat so it is a much better foundation. It will take a long time to reach parity with vscode but when it does it will smoke it.
That doesn't mean Zed will have all the other extensions that VS Code has... Recently added the new SQL Server extension(s) and it's been at least interesting, in a way slightly better than using SMMS. It's pretty much burrowing the UI from Azure Data Studio (or whatever it was called). Haven't tried similar for PG/SQLite etc yet.
I don't know, it feels like Zed popularity is just people chasing the latest editor hotness, a time-honored traditional programmer ritual to be sure, but still, just a ritual. And now it seems zed devs have to put AI in front of all other initiatives, probably because of the VC funding they took.
I could see not wanting to use VSCode for other reasons, like MS pivoting back to "be evil", but at least in my little bubble, performance is not one of them.
Memory usage of the IDE doesn't matter much when your language servers can eat 10s of gigs of RAM.
I tried Zed several times and I just don't see the point.
The main issues with VScode over something like the Jetbrains IDEs is that language servers are just not as powerful or as integrated to the IDE as the Jetbrains solution can be and Zed does nothing to solve it.
I don't think it being a native app offers much added value.
I wonder why the startup time is slow though, may have to debug that one.
It is an editor made for people who are used to double-clicking individual files rather than opening a folder in VS Code, so they close and open their editor dozens or even hundreds of times per day.
Let's say VS Code takes 5 seconds to boot.
Some programmers may argue: "yes, I spend 3 hours on a project or just leave it open overnight, so 5 seconds per week is nothing"
But here is not the case, it is for programmers who come from Notepad/Sublime/Notepad++/emacs/vi, and who opens a single file and closes the editor right after.
If you work 2 hours, maybe 4 files per minute, this means 120 * 4 openings = 480 openings.
It means you would have wasted 2400 seconds (40 minutes per day!) waiting for VS Code to open (about 33% of the 2-hour work session spent waiting)
Yes, like with Notepad or Zed, you lose some features like Colors or Syntax checking, but still, time is the most precious thing in life.
For users who come from very advanced but slow text editors like Microsoft Word (used in coding exams: https://stackoverflow.com/questions/76102874/single-and-doub... or programming courses: https://youtu.be/0TVugOJtAiU?t=162 ), this is truly revolutionary and life-changing.
How can any software developer work when they need to open and close 4 files per minute? I have never met or heard of anyone working like this.
In this demographics, hype rarely is connected to technical qualities, they are used more as a post-hoc rationalization.
Instead of learning from what worked and fixing what didn't, they just threw everything away and wandered off in some totally different direction. They did the reactionary kind of learning instead of the theory-building kind: https://xkcd.com/242/