Live data from Hacker News

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

zed.dev

211–220 of 301 posts

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

#211
post #84
post #79

Earlier quoted context omitted.

> Other than that for anyone wanting to try Zed: Also, no support for debugging yet.

You do not need debugging if you have AI.

Yeah, this is a moronic take. I'm all in on AI programming, but when you need debugging, you really need it - sometimes the model will get utterly fixated on a solution that is just wrong, and you just need to follow the stack trace.

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

#212
post #154

Earlier quoted context omitted.

New York at one point had 150,000 horses, each producing 15 to 30 pounds of manure daily. On top of that they produced 40,000 gallons of horse urine. Imagine the stench. https://danszczesny.substack.com/p/the-great-horse-manure-cr...

While I certainly would not advocate going back from vehicles to horses, I would observe that the replacement for horses had even more toxic emissions. Particularly in the era of leaded gasoline. The smell of manure was far less damaging .

[deleted]

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

#213

Earlier quoted context omitted.

I think there may be a good point here, but it's buried in a wall of poorly-written text and inappropriate references to your relationship problems.

Finding a way to complain about your wife in a comment about an IDE is peak hacker news.

Perhaps, but using a marriage as an analogy for one's preferred IDE doesn't seem like a huge stretch.

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

#214

Earlier quoted context omitted.

> a private key or API key could get sent, right? You can disable this feature on a per-file basis, here’s the relevant setting: https://github.com/zed-industries/zed/blob/39c9b1f170cd640cd...

Sending files to a remote server is never something that should need to be disabled, this must be an opt-in or it's time for a fork.

It is opt in. You have to manually sign in to Zed and enable the feature.

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

#215
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.

[deleted]

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

#216
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…

I don't think this is a concern. Zed and Zeta are both open source. Fork it, self host it, whatever.

Absolutely. This is already what I've been doing myself. Forked zed so I could use my local rig (4x 3090) to do FIM completions using a finetuned qwen coder 32B.

Only barrier for some folks will be if they're not familiar with rust or local LLMs in general, but it really wasn't that difficult looking back on it. Amounted to about an afternoon's worth of work.

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

#217
post #79

Earlier quoted context omitted.

> Other than that for anyone wanting to try Zed: Also, no support for debugging yet.

I asked them about this on X and they are working on one. I use Zed for everything now but must keep VS Code around just for the debugger. I can't wait to delete it.

Debugger PR is here https://github.com/zed-industries/zed/pull/13433 if you want to check it out

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

#218

Earlier quoted context omitted.

Even if you know how much it costs, how can you be sure they won't increase the price later on?

Is there anything worthwhile that costs the same now that it did 50 years ago?

Why is 50 years your timeframe? I'd be more curious about cost increases a year, two years down the line.

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

#219
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…

That's ... uh ... not what a rug pull is. They're telling you plainly from the jump that they're going to eventually charge for it. Point taken on your wish to wait, that makes perfect sense.

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

#220

Earlier quoted context omitted.

> a private key or API key could get sent, right? You can disable this feature on a per-file basis, here’s the relevant setting: https://github.com/zed-industries/zed/blob/39c9b1f170cd640cd...

Sending files to a remote server is never something that should need to be disabled, this must be an opt-in or it's time for a fork.

Agreed. The predict edit feature needs to be actively enabled before it'll do anything. And once it's enabled, it won't send up your private keys or environment variables. If their filename matches a glob in this list, or a list you configure.
Post reply on HN