41–45 of 45 posts
Quoting from the README: > The entire VSCode workbench - editor, terminal, extensions, themes, keybindings — ported to run on a native shell. but also > Many workbench features are stubbed or partially implemented So which is it? The README needs to be clearer about what is aspirational, what is done, and what is out of scope. Right now it just looks like an LLM soup.
> Goal: 200mb RAM usage This is why Zed is great but I just can't get used to the debugger experience so I end up back in VSCode.
Earlier quoted context omitted.
Paraphrasing. > There’s a new kind of coding I call “hype coding”, where you fully give in to the hype, embrace exponentials, and forget that the product even exists.
Isn't this basically what was happening with most of our personal projects coming from ideas that we found very interesting and then forget that we ever thought about it?
Earlier quoted context omitted.
Not op but there is a lot of details about VS code including electron that could have been done better.
That can be said about any project. And VSCode as been improving since inception, hence why it ate a large pie of the market.
Earlier quoted context omitted.
That can be said about any project. And VSCode as been improving since inception, hence why it ate a large pie of the market.
I think the exact opposite, this why alternatives like Zed is taking off.
And did they implement debugger support?
When I need a barebones editor I reach for Sublime which doesn't market themselves as something else.
As for Zed taking off, I see a lot of vocals in some niche communities but they barely register, if at all, in large annual surveys.