Most active commenters
  • veber-alex(3)

←back to thread

677 points meetpateltech | 13 comments | | HN request time: 0.001s | source | bottom
Show context
extr ◴[] No.45117263[source]
Zed is so great, I do wish they would focus just a little bit more on bringing the UI just a bit more up to parity with VS Code, I would switch full time.
replies(3): >>45117325 #>>45117438 #>>45118430 #
TheRoque ◴[] No.45117438[source]
What's so great about zed ?
replies(4): >>45117489 #>>45117862 #>>45118952 #>>45124588 #
1. digitaltrees ◴[] No.45117862[source]
It’s built by the team that built atom which was way better than vscode but was mothballed when Microsoft bought GitHub.

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.

replies(1): >>45118796 #
2. veber-alex ◴[] No.45118796[source]
So...nothing.
replies(3): >>45119387 #>>45119611 #>>45162191 #
3. robinhood ◴[] No.45119387[source]
Your comment is as insulting as it is indicative of a complete lack of knowledge about the world of editors and software development in general.
replies(2): >>45119606 #>>45119802 #
4. veber-alex ◴[] No.45119606{3}[source]
If you think "build by atom team" and "not electron" are any kind of serious advantage for any peace of software than your are the one who lacks knowledge about software development.
replies(1): >>45119614 #
5. rvnx ◴[] No.45119611[source]
I think you do not understand the value proposition of Zed.

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.

replies(3): >>45119775 #>>45121680 #>>45121704 #
6. rvnx ◴[] No.45119614{4}[source]
Made me think about: https://news.ycombinator.com/item?id=43041923 where they mention Atom as well
replies(1): >>45125318 #
7. veber-alex ◴[] No.45119775{3}[source]
You are right. I don't understand.

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.

replies(1): >>45120229 #
8. sexyman48 ◴[] No.45119802{3}[source]
A complete lack of knowledge? At least GP understood 90% of his peers don't know vscode is built on a browser framework, and wouldn't care.
9. typpilol ◴[] No.45120229{4}[source]
Right lol. It's so ridiculous
10. ◴[] No.45121680{3}[source]
11. bergheim ◴[] No.45121704{3}[source]
This has to be a joke.

No one ever closes emacs.

12. conartist6 ◴[] No.45125318{5}[source]
It would be relevant that they were the team behind Atom if they seemed to understand the lessons of Atom...

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/

13. digitaltrees ◴[] No.45162191[source]
Did you miss the point about it being built on a fundamentally better tech stack by a team with a track record of better design decisions?