Live data from Hacker News

Zed 1.0

zed.dev

291–300 of 727 posts

Re: Zed 1.0

#291

I tried Zed several times, and still VS Code + Sublime win. 1. In Zed, all my Rust files are reformatted on save. (I also code in Go, and don't like this approach at all.) 2. It takes ages to find out where to configure the language servers, and find those little options several layers deep, that I need to switch. (E.g. turn of rustfmt, or turn off some PEP8 checks.) 3. Zed is still missing the killer feature of Rust…

1. That's a pref, turn off "format on save" lots of editors and IDEs have it. Maybe they should default to off but it's not an unheard of option with no way to turn off.

Re: Zed 1.0

#292
post #156

Earlier quoted context omitted.

What is Ghostty's advantage over Alacritty?

The maintainer doesn’t have bad temper.

I did consider that. I remember nope-ing out of alacritty in the early days after seeing the developers response to people requesting a scrollback buffer. It amounted to something like "I use tmux, and if you don't, you use the terminal wrong." It left a bad taste in my mouth.

Re: Zed 1.0

#294
This is a solid release and first time, I feel like it is pretty good for the use case of decent sized Typescript mono repos. I can jump around codebase quicker.

PS: Pretty daring move to think of building an editor when there's already sublime, textmate, Jetbrains and VSCode.

Re: Zed 1.0

#295
post #273

Earlier quoted context omitted.

> I love Sublime, but I don't want to pay to upgrade from 3 to whatever version it is now I don't know what your financial situation is, but given that the upgrade is an $80 one off payment (a new license is $99), that it's a per-user license (not per-machine), and that there were 8 years between Sublime Text 3 (2013) and Sublime Text 4 (2021) (only major versions require a new license), I personally think it's very…

It is "one time" in the sense that it will never stop working, unlike a subscription model. You are however limited to 3 years of updates, so if you want to keep up to date, it is $80 for 3 years. Which if fine for me, it is the one piece of software I used the most except for the browser and OS, I even use it to make money, $80 / 3 years is not much. It is also the kind of software I like to support. It is... respec…

Ah, you are correct. I thought a renewal was only required for a new major version after 3 years. But it's actually any update after 3 years. Which is still pretty reasonable (but not quite such a good deal)!

Re: Zed 1.0

#296
post #253

Earlier quoted context omitted.

windows makes it really hard to distribute applications now. everything gets a warning until the app has some minimum count of installs

>everything gets a warning until the app has some minimum count of installs Unless the devs sign their app

So then the question is, why haven't they?

Re: Zed 1.0

#297
post #254

Congrats! My daily driver is Zed developing on SSH remote servers on exe.dev. It's crazy to think of all the dev tools I've churned through over the last 18 months but these two feel sticky. Zed has everything I need in a unified pane. File editor, terminal, agents, SSH remotes. And it's fast and intuitive exe.dev is the first "dev container" I've ever *loved*. The remote sandbox means `dangerously-skip-permissions`…

"online live reloading apps" => trying to get my head around this workflow. so the disk is shared across these? so do you still have the problem of say running a "main" version of an app, and it's weird experimental version of that same app? because they still have to live in different folders/worktrees? that's where I get stuck a little trying to enable things like this for others. right now, I've got people a syste…

Yes I’m trusting exe.dev disks and persistence.

For many apps the weird experimental version is all there is. Call it vibe coding or experiments or non-critical tools. These may not even have a GitHub repo. I trust local git and the exe.dev disks.

Then for serious apps the above is the same shape for development branches. Spin up a VM in a few seconds with the code checked out and running online and editable over an SSH mount is the magic.

Then that turns into a PR on GitHub and a normal review then CI/CD to staging and prod takes over.

Re: Zed 1.0

#298

Earlier quoted context omitted.

> It would be great if it supported more commands though! What does it not support? I want to try and figure out if its shortcomings in the ACP/Claude SDK or if it's just features that Zed has yet to support?

Context length is not shown and I dont think you can paste images? Havent tried though

Context usage is in an open PR now! https://github.com/zed-industries/zed/pull/54881 give it a week or two depending on if you want to use stable vs preview releases. I haven't tried pasting images yet either but I have used their context menu that lets you add images.

Re: Zed 1.0

#299
post #90

Earlier quoted context omitted.

> My code (which works fine) looks like an ocean of red when I view it with Zed, and turning all those warnings off is not trivial. Isn't it just the default configuration of whatever LSP zed defaults to for PHP? So you should be able to either configure the LSP to avoid that or disable the LSP server entirely.

Coming from Sublime, I'd never even heard of a Language Server when I first tried Zed. As I recall, disabling particular kinds of warnings required copy-pasting some pretty exotic incantations into my project config. All of it was poorly documented, and it felt like I was doing something nobody expected me to do. Instead, I should have been able to mouse over a particular warning and say "don't warn me again about th…

Yeah, I really can't stand every vscode has done to the ecosystem for settings. JSON as a storage format for config is entirely fine, but it's a truly awful UX for changing things. But they're successful and it's easy to build, so everyone mindlessly copies them.

Re: Zed 1.0

#300
post #97

What an abysmal series of top comments. These guys created a phenomenal product using novel technology, which will only continue to improve. Great work to the Zed team.

I hope HN can appreciate what a game changer (and paradigm shift) Zed can be.

To the Zed developers: CONGRATULATIONS! I have been following your project with great interest since your speed demo years ago. And since it’s AI-first, I’m interested to see how we can integrate it with https://safebots.ai (Safebots, Safebox, and Safecloud).

I would love to see how we might be able to increase the safety of agents in Zed, use local models like Qwen/Deepseek and we also have Grokers which can turn any codebase into a graph with tree-sitter and help your agents far more than RAG and similarity search (https://grokers.ai/deck.pdf)

What’s the best way of getting in touch? (If you want, my profile has a way of emailing me).

Post reply on HN