Earlier quoted context omitted.
Complexity for the sake of complexity is not a goal everyone should be striving for.
> Complexity for the sake of complexity is not a goal everyone should be striving for. THIS ! Go's well maintained stdlib just lets me get on with it. With Rust meanwhile, I have to decide which of thousands of third-party Rust crates is sufficiently en-vogue and well maintained. Most of my coding work is backend stuff that calls a lot of HTTP APIs, parses a lot of JSON and does a lot of crypto. All that is ready-to-…
Zed is our office
311–320 of 343 posts
Re: Zed is our office
#312Earlier quoted context omitted.
I used to only use JetBrains for AI stuff, now I just open everything in Zed because of its Claude Code integration. Especially with the linters and other nice to haves. I am insanely close to cancelling JetBrains.
Theres a plugin for Claude Code and you can use Claude models from Copilot in IntelliJ. Are those options worse than Zed, especially considering other comments about Zed missing basic editor stuff?
Re: Zed is our office
#313Earlier quoted context omitted.
I used to only use JetBrains for AI stuff, now I just open everything in Zed because of its Claude Code integration. Especially with the linters and other nice to haves. I am insanely close to cancelling JetBrains.
JetBrains products has Claude Code integration. Is it worse? I still use Claude Code in cli, as a WebStorm user.
Theres two ways to use Claude Code in JetBrains and instead of helping them make their plugin better they opted to try and make money off of it. Which Zed could have done the same but instead lowered their monthly to let you use your own Claude Code subscription.
Re: Zed is our office
#314I generally like what Zed is trying to become. However, all of these features and blog posts are frustraing when they struggle to keep basic editor features stable. Edit a file outside of the editor? It's not going to show up in the project pane or the git diff. Need to work inside a container because it's 2025 and we don't need to clutter our local machine with 100s of dependencies and env managers... well now all t…
Re: Zed is our office
#315Re: Zed is our office
#316I also kind of get why it's built into an editor! I wonder how it compares to e.g. https://www.coscreen.co.
The default method of remote work, with e.g. Slack and video meetings, I think leaves a lot of potential on the table. I wonder if a flexible collaboration system like this could actually be a lovely default method for many companies.
Re: Zed is our office
#317Earlier quoted context omitted.
ohhh... is this that thing where people say "blurry" to describe anti-aliasing, because they actually want it to be pixelated?
Nope, it is the thing where people say "blurry" to describe "blurry". https://github.com/zed-industries/zed/issues/7992#issuecomme... This is how Zed looks like on my computer too. VSCode manages to render things crisply while Zed is a blurry mess.
Re: Zed is our office
#318Earlier quoted context omitted.
ohhh... is this that thing where people say "blurry" to describe anti-aliasing, because they actually want it to be pixelated?
Nope, it is the thing where people say "blurry" to describe "blurry". https://github.com/zed-industries/zed/issues/7992#issuecomme... This is how Zed looks like on my computer too. VSCode manages to render things crisply while Zed is a blurry mess.
Re: Zed is our office
#319Whenever a product tries to be too many things, it dilutes the core USP. Try to be an excellent code editor. Add extensibility. Done. I get it, you are VC funded, investors want to turn this into a multi billion dollar unicorn. Do not focus on investors, but developers.
As mentioned in the post, Zed's collaboration functionality is its core USP. The entire editor was literally built around it. IIUC their moonshot is to replace the GitHub PR model with something more collaborative and granular.