Live data from Hacker News

Zed now predicts your next edit with Zeta, our new open model

zed.dev

121–130 of 301 posts

Re: Zed now predicts your next edit with Zeta, our new open model

#121
post #48

Earlier quoted context omitted.

If you fight the system you're not going to have a good time. For incremental improvements (faster grep, mixed-language syntax highlighting) you get the benefits for free. You don't have to change anything about the way you work. Revolutionary/disruptive technologies are not like that. They demand that the world adapts to them. They demand you change. Almost anywhere you can go by foot you can get faster with a horse…

We paved the world and now it’s fucked — progress is not always a good thing, in this case it was a mistake that we and our descendants will continue to pay the price for.

Indeed, calling it “progress” is political.

Re: Zed now predicts your next edit with Zeta, our new open model

#122
post #81
post #47

> Edit prediction won't be free forever, but right now we're just excited to share and learn. I love Zed, and I'm happy to pay for AI stuff, but I won't be using this until they are done with their rug pull. Once I know how much it costs, I can decide if I want to try integrating it into my workflow. Only THEN will I want to try it, and would be interested in a limited free trial, even just 24 hours. Considering I've…

Hey, my name is Piotr and I work on language servers at Zed. Right now you can run multiple language servers in a single project. Admittedly you cannot have multiple instances of a single language server in a single worktree (e.g. two rust-analyzers) - I am working on that right now, as this is a common pain point for users with monorepos. I would love to hear more about the problems you are having with running langu…

Hi, thank you. I specifically meant running multiple LSPs in the same file at the same time, akin to vscode.

Re: Zed now predicts your next edit with Zeta, our new open model

#123
post #45

Earlier quoted context omitted.

I find that AI autocomplete, even autocompleting full functions, is capable enough to use. I need to review all my code in detail before pushing, and I need to write unit tests, and I need to "run it once" test it also. It gets it mostly right most of the time, and often times it quite literally suggests what I was about to type. This is mostly in Rust and C#, maybe other languages have more of a hurdle for AI.

So it can rust now? That's impressive! Last time I tried it had no way of valid rust code beyond hello-world level, constantly producing code that failed the borrow checker.

I rarely if ever have to worry about the borrow checker, mostly stumbling blocks are move/copy/clone semantics.

GitHub Copilot does a good job of generating correct Rust, it just has the usual subtle-but-annihilating-if-not-caught logic bugs, like in all other languages.

Re: Zed now predicts your next edit with Zeta, our new open model

#124
post #3

I tried CoPilot a while and my biggest gripe was tab for accepting the suggestion. I very often got a ton of AI garbage when I was just trying to indent some code. Tab just doesn't seem like the proper interface for something like this.

Yes, copilot's tab in vim is that made me think that AI is useless. However next iteration of AI coding tools made me rethink this (I am using https://github.com/olimorris/codecompanion.nvim with nvim now).

Re: Zed now predicts your next edit with Zeta, our new open model

#125
As a slight tangent, this prompted me to wonder about one of the things I _haven't_ enjoyed in my last two weeks of experimenting with zed: It tries to autocomplete comments for me. Hands off - that's where I think!

Fortunately, zed somewhat recently added options to disable these:

   "edit_predictions_disabled_in": ["comment"],
   "inline_completions_disabled_in": ["comment"]
My life with zed just got a little better. If I switch back to vscode I'll have to figure out the same setting there. :-)

Re: Zed now predicts your next edit with Zeta, our new open model

#126
post #85

Earlier quoted context omitted.

Hey! Zed founder here. We totally agree with this and that's why Zed will switch the keybinding for accepting an edit prediction to `alt-tab` when the cursor is in the leading whitespace of a line. This way you can keep using `tab` for indenting in that situation. Also, when there's both an edit prediction and and LSP completion, Zed switches the keybinding to `alt-tab` to prevent the conflict with accepting an LSP c…

For reasons that should be obvious, that's not going to work on Windows.

Sorry, I assumed macOS: but you're right! For Linux (and Windows, once we ship support for it) the keybinding is alt-l to avoid conflicting with tab switching.

Re: Zed now predicts your next edit with Zeta, our new open model

#127
post #58

Earlier quoted context omitted.

yeah, i'd like to be able to run it locally. it should fit well onto my 12gb gpu

The model is based on Qwen2.5-Coder-7b it seems. I currently run some quantized variant of Qwen2.5-Coder-7b locally with llama.cpp and it fits nicely in the 8GB VRAM of my Radeon 7600 (with excellent performance BTW), so it looks like it should be perfectly possible. I would also only use Zeta locally.

Are you happy with the speed with your 8GB GPU?

Re: Zed now predicts your next edit with Zeta, our new open model

#130
post #3

I tried CoPilot a while and my biggest gripe was tab for accepting the suggestion. I very often got a ton of AI garbage when I was just trying to indent some code. Tab just doesn't seem like the proper interface for something like this.

It's way better than the other Microsoft favorites of space and enter...

It's as if people developing autocomplete doesn't really code.

Post reply on HN