Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code: Now in Beta in Zed

zed.dev

Post reply on HN
Print view View original

221–230 of 431 posts

Re: Claude Code: Now in Beta in Zed

#221

Post by ricardobeat »

EnPissant wrote: post #204
freehorse wrote: post #147

Earlier quoted context omitted.

While I do not doubt that there are people who experience this on some monitor/OS combinations, I have used zed on basic 1080p and 1440p 24" monitors with no issue. Sometimes I have general issues with some monitors in macos, which is usually due to some super-resolution/sharpness setting on the monitor itself that I need to adjust, but nothing specific to zed. All I say is that these issues are far from universal wi…

You may not notice because macOS fonts look terrible (blurry) on any monitor that is not hidpi. Zed is just par for the course here. Meanwhile on Linux and Windows, they still implement subpixel rendering so fonts look great on 1440p.

This discussion goes back twenty years, with Apple going for preserving the original typeface appearance over crispness. It depends what you value the most and is entirely subjective.

Re: Claude Code: Now in Beta in Zed

#222

Post by ricardobeat »

aseipp wrote: post #129
modernerd wrote: post #89

Earlier quoted context omitted.

> Configuration is all JSON Curious as someone dabbling with building an editor: what do you prefer? A different configuration language? A GUI? How do you save and sync settings? Just with JetBrains account sync? > Ability to move panels (files/git/console/debugger/etc) into standalone windows Is Zed's "zoom in" feature (shift-escape) that quickly maximises the active pane (excluding the file browser/git pane) enough…

Yes, a GUI for settings is nice if only for one thing: so there can be a search box that you can use to search over all the settings to find what you need in a pinch. It's a lot friendlier if I can do something like "Open Settings > Ctrl+F > 'Font'" or whatever than having to go find the manual and look it up. I don't care about the configuration language so much personally (though JSON is of course pretty lame in a…

You get almost the same effect by typing “font” as a config key and going over autocomplete suggestions.

Re: Claude Code: Now in Beta in Zed

#223

Post by ricardobeat »

WA wrote: post #52
kenhwang wrote: post #43

Earlier quoted context omitted.

Top of my head switching between IntelliJ and Zed: - Git UI is extremely barebones with no support for other VCS - No merge tool or side-by-side diffs - Configuration is all JSON - Would be nice having a full file tree for the search editor instead of just the list; having the functionality split between a tab and the outline panel is quite clunky. - Ability to move panels (files/git/console/debugger/etc) into standa…

No side-by-side diff is a deal-breaker for me unfortunately.

This is a great divider between people who want an IDE vs a text editor - Zed explicit is the latter.

Re: Claude Code: Now in Beta in Zed

#224

Post by ricardobeat »

neurostimulant wrote: post #175

It's great that Zed adding this very useful feature, but isn't this effectively cannibalize their own AI subscription plans? Why pay zed $20 when you already pay for claude code and can use it in the assistant panel? You might still want the edit prediction feature, but then why pay zed $20 when you can pay $10 github copilot and can use it to power zed's edit prediction feature?

It’s also great that they’re willing to risk that, in the name of a potentially better user experience. That’s what gets them to win in the long run, not building another walled garden.

Re: Claude Code: Now in Beta in Zed

#225

Post by EnPissant »

ricardobeat wrote: post #221
EnPissant wrote: post #204

Earlier quoted context omitted.

You may not notice because macOS fonts look terrible (blurry) on any monitor that is not hidpi. Zed is just par for the course here. Meanwhile on Linux and Windows, they still implement subpixel rendering so fonts look great on 1440p.

This discussion goes back twenty years, with Apple going for preserving the original typeface appearance over crispness. It depends what you value the most and is entirely subjective.

There are 2 issues on Apple:

1) How much font hinting to apply. More hinting changes the shape to make glyphs line up better with pixels so that less antialiasing is required. macOS prefers very light hinting to preserve shapes at the cost of blurriness. This is what you are talking about.

2) Subpixel rendering. This effectively triples the horizontal resolution when rendering fonts, and does not affect the shape at all. Fonts look dramatically better on normal dpi displays when using it. macOS removed support for this many years ago. This is what I'm talking about.

Re: Claude Code: Now in Beta in Zed

#226

Post by beckler »

TiredOfLife wrote: post #217
cnqso wrote: post #162

Earlier quoted context omitted.

What Zed lacks in code generation quality it makes up for in not-being-an-Electron-app

Zed includes node.js runtime and 100s of megabytes of javascript. It is essentially Electron.

I'm gonna need you to back that claim up dawg, because the only thing I see the node runtime used for, is for when the user loads a js project.

then it's basically just a proxy for node/npm afaik.

Re: Claude Code: Now in Beta in Zed

#227

Post by sxg »

yes_but_no wrote: post #165
unshavedyak wrote: post #111

I want to try Zed but the Helix mode seems quite young. Vim mode sounds good, but i just can't move away from Helix mode. (oh and of course, my own modifications to Helix's input config) My difficulty in finding editors that fit my desired input scheme kinda reminds me of the old pre-LSP days. Where you'd chose an editor based on it's language features. I wonder if we need some sort of common editor interface to allo…

If you are already familiar with Vim bindings is Helix's object then action really worth that much?

I thought the same, but I gave Helix a shot for fun a couple years ago and never looked back. It really does feel better/more ergonomic, but the greatest benefit is that almost everything you need is built in. I spent way too much time fiddling with Vim and NeoVim configs.

Re: Claude Code: Now in Beta in Zed

#228

Post by fkyoureadthedoc »

cyanf wrote: post #176
hu3 wrote: post #122

Earlier quoted context omitted.

> Wow. This might be the 1st time i've seen someone comment negatively regarding UI performance Here you go: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... > I found Copilot tab completion completion to be VERY slow in Zed, for some reason. > Zed still takes a relatively long time to start on my old desktop. I thought something was wrong but no, it is just THAT slow > I have tried it out and by defau…

The other examples you listed are valid, but A.I tab auto complete is a model & inference issue unrelated to the editor.

Idk if 'linux + gpu = problem' is surprising or very relevant either.

Re: Claude Code: Now in Beta in Zed

#229

Post by veber-alex »

robinhood wrote: post #212
veber-alex wrote: post #160

Earlier quoted context omitted.

So...nothing.

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.

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.

Re: Claude Code: Now in Beta in Zed

#230

Post by rvnx »

veber-alex wrote: post #160
digitaltrees wrote: post #70

Earlier quoted context omitted.

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.

So...nothing.

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.

Post reply on HN