101–110 of 277 posts
Zed seems really nice, and the usability has come a really long way in the last couple of months. That being said, I have one issue, and I hesitate to even bring it up because it seems so shallow: I hate all the themes! They all look so ugly and amateur. I know this is a really trivial thing, it's like complaining I don't like Python because it uses whitespace for indent or something, but I just can't get over it. VS…
Zed seems really nice, and the usability has come a really long way in the last couple of months. That being said, I have one issue, and I hesitate to even bring it up because it seems so shallow: I hate all the themes! They all look so ugly and amateur. I know this is a really trivial thing, it's like complaining I don't like Python because it uses whitespace for indent or something, but I just can't get over it. VS…
There's also an importer tool [1] that lets you convert any VS Code theme to a Zed theme. You might still need to compile the importer yourself, but it's all pretty straightforward.
0: https://github.com/zed-industries/zed/discussions/7337
1: https://zed.dev/blog/user-themes-now-in-preview#using-a-vs-c...
Earlier quoted context omitted.
Disabling JS is incredibly beneficial for browser performance, battery life, privacy/tracking protection. As an added bonus, it protects you from malware from all the vulnerabilities in Javascript engines.
Which vulnerabilities in the past few years were actually used as a way to propagate malware (Not targeted 0-days)? Even with a JS engine vulnerability, you'd still need a sandbox escape to do something useful with it
Zed seems really nice, and the usability has come a really long way in the last couple of months. That being said, I have one issue, and I hesitate to even bring it up because it seems so shallow: I hate all the themes! They all look so ugly and amateur. I know this is a really trivial thing, it's like complaining I don't like Python because it uses whitespace for indent or something, but I just can't get over it. VS…
And then, due to speed, there is no going back to the lag infested chromium derivative made by Microsoft.
This is great. I just hope that they continue to make money. We really need someone to invest in making a Fast, modal editor.
Does Helix fit that bill for you? It's fast, modal and very little config required. I think there's also a fork if you can't let go of the VIM bindings.
The fuck-off-if-you-don't-agree-with-me dictator of the project doesn't help either.
What I'd really like is an option to disable the automatic multi-buffer behavior for things like git diffs. It just doesn't work for me, and the Zed UX seems to not even realize that not everyone will love it.
I think this is one of the best innovations in Zed, though it could use some more polish to work really great. Being able to edit the diff directly surely is a great thing?
Total nitpick, but: Why would you name an option "disable_ai" with a default value of false instead of calling it "enable_ai" with a default value of true? Are there some mechanical semantics I'm missing here that make this beneficial? Negative booleans (ie that remove or suppress something when true) are generally a source of confusion and bugs and should be avoided like the plague in my experience.
I think it's reasonable to, for example, have a field that is labeled "Do Not Track".
Zed seems really nice, and the usability has come a really long way in the last couple of months. That being said, I have one issue, and I hesitate to even bring it up because it seems so shallow: I hate all the themes! They all look so ugly and amateur. I know this is a really trivial thing, it's like complaining I don't like Python because it uses whitespace for indent or something, but I just can't get over it. VS…
Total nitpick, but: Why would you name an option "disable_ai" with a default value of false instead of calling it "enable_ai" with a default value of true? Are there some mechanical semantics I'm missing here that make this beneficial? Negative booleans (ie that remove or suppress something when true) are generally a source of confusion and bugs and should be avoided like the plague in my experience.
They had AI features that were always on.
Some people complained so they introduced a flag to, wait for it, disable the ai features.
So they didn't think too deeply about it and named the flag "disable_ai" because it mapped into how they were thinking about it.
You overstate the problem with negative booleans. It's trivial for them to add a function:
fn isAiEnabled() { return !disable_ai }