Live data from Hacker News

Zed AI

zed.dev

291–299 of 299 posts

Re: Zed AI

#291

Not releasing a cross-platform code editor on the dominant OS seems quite weird in my opinion. (I know they plan to do it, but as someone who has built cross-platform apps, this is not rocket science to have Win32 support from the start.)

It's especially weird they released linux (with x11 AND wayland backends) before windows.

For the kinds of devs they've hired, Windows is the third most common development or production environment. I've worked at startups like this for 20 years and haven't touched a windows system.

I realize yall are out there, but from where I'm sitting, this isn't odd at all. They're likely most familiar with and using Unixes.

Re: Zed AI

#292
post #230

Earlier quoted context omitted.

Kubernetes, AWS, Cloudformation and Terraform etc sort of work is still not good with AI. The current AI code rocket ship is VSCcode + Perl/Python/Node+ReactJS + Co-Pilot. This is basically a killer combination. Mostly because large amounts of Open source code is available out there for training models. Im guessing there will be an industry wide standardisation, and Python use will see a further mad rise. On the long…

> For now, forget about golang I write kubernetes controllers. Golang is here to stay. > Just use Python for turbo charged productivity This is my problem with all the "AI" bros. They seem to consistently push the idea that quickly writing code is the end all of "productivity" its akin to "just shovel more shit faster its great" Speed != productivity

I have seen several rounds of this over decades. Google will make bad programmers, Perl is a write only language, Node is cancer, Eclipse is slow etc etc.

Eventually you realise you just can't win against better things. These are juggernauts, fighting them is pointless. Because it doesn't matter when you use it or not. Most people will, and make great progress.

You will either be out of the industry or be forced to use it one way or the other.

Re: Zed AI

#293

Earlier quoted context omitted.

I'm curious, what kind of work do you do? Does stack overflow slow you down?

I'm just as baffled by the people who use stackoverflow daily. Its increasingly rare that I use it these days, to the point where I deleted my account a few years back and haven't missed it. Don't people read docs anymore? In many ways I feel lucky that I learned at a time when I only had offline docs, which forced me to become good at understanding documentation since its all I had.

To give you some insights from someone with a different starting point:

For context I'm a 22 year old CS student and part-time SRE working on everything related to kubentes (golang, scripting, yaml, ...). I can assure you that reading the fucking manual isn't a thing my fellow students or I did when we could avoid it. I think that might be because university projects don't tend to be long lasting and finding quick pre build solutions - without understanding them - works just fine. There is no penalty for technical debt.

Now almost exclusively read the primary docs or code and I think that might (surprisingly?) be because of copilot.

The neovim copilot extension resulted in me not feeling the need to switch to my browser all the time. Not having to do this context switch and looking more at my code got me into reading the lsp provided symbol docs. After some time I noticed that copilot just made me feel like I know what I'm doing and reading the overlay docs provided a way deeper understanding.

Re: Zed AI

#294
Sorry if this comes off as entitled, I'm honestly just a bit confused by the following.

I have no experience using (current) vscode, but I've used neovim on a daily basis for a couple of years. I think the thing which makes an editor a "better editor" are the small things, things which solve problems which might cause a little friction while using the editor. Having a lot of these little points of friction results in a (for me) annoying experience.

Zed has a lot of these (from the outside) simple issues and I don't see them working on them. Again, I understand that they have to prioritize. But this doesn't result in me feeling comfortable spending time adopting this editor. I'm "scared" that issues like https://github.com/zed-industries/zed/issues/6843 might be very low on the list of work being done and always will be, while the next big (maybe honestly great) feature gets all the attention.

Re: Zed AI

#295

Earlier quoted context omitted.

I'm just as baffled by the people who use stackoverflow daily. Its increasingly rare that I use it these days, to the point where I deleted my account a few years back and haven't missed it. Don't people read docs anymore? In many ways I feel lucky that I learned at a time when I only had offline docs, which forced me to become good at understanding documentation since its all I had.

To give you some insights from someone with a different starting point: For context I'm a 22 year old CS student and part-time SRE working on everything related to kubentes (golang, scripting, yaml, ...). I can assure you that reading the fucking manual isn't a thing my fellow students or I did when we could avoid it. I think that might be because university projects don't tend to be long lasting and finding quick pr…

Thanks for the perspective!

Do you think this helps or hinders your ability to internalise the information (ie so that you don’t need to look it up, in the browser or from the LSP)?

For me, I feel that documentation is a starting point, but the goal is always to not need to look it up, after a little ramp up time.

With that said, I do use ChatGPT as a replacement for documentation sometimes, asking it how to do things instead of looking it up, but again the goal is to internalise it rather than to rely on the docs or tools. I won’t shy away from reading primary documentation, though, when necessary.

Re: Zed AI

#296
post #67

Earlier quoted context omitted.

This feature does exactly that. You can open up the chat panel, run "/tab name-of-tab" or "/file path-to-file" and then start asking questions about the code.

Hey! I'm Nate from Zed. You can also use the /file command to drop entire directories, or even globs into the assistant. For example, you can do /file *.rs to load all of the rust files in your project into context. Here is a simple but real example I used a while back: "/file zed/crates/gpui/src/text_system.rs I have a font I want to check if it exists on the system. I currently have a &'static str. Is there somethi…

Loading a large number of files into context uses up a lot of the context length and may often even exceed the context length of the LLM. Is there any RAG-like feature planned so that only relevant parts of the code are loaded?

Re: Zed AI

#297

Earlier quoted context omitted.

To give you some insights from someone with a different starting point: For context I'm a 22 year old CS student and part-time SRE working on everything related to kubentes (golang, scripting, yaml, ...). I can assure you that reading the fucking manual isn't a thing my fellow students or I did when we could avoid it. I think that might be because university projects don't tend to be long lasting and finding quick pr…

Thanks for the perspective! Do you think this helps or hinders your ability to internalise the information (ie so that you don’t need to look it up, in the browser or from the LSP)? For me, I feel that documentation is a starting point, but the goal is always to not need to look it up, after a little ramp up time. With that said, I do use ChatGPT as a replacement for documentation sometimes, asking it how to do thing…

> Do you think it [copilot?] helps or hinders...

It showed me some nice shortcuts (quick anon js functions and the like) which I will be using in the future, but I noticed that I didn't remember multi step code flows. For example while trying to get the response from an http request in go, there is a chain of calls which you will most likely follow. Building the client > making the request > checking the response code > reading the body > maybe parsing the body if it's structured text. I had written this kind of flow hundreds of times while having copilot running, and I still could not write it myself - I just had this abstracted idea of what's happening, but no memory of the syntax.

> as a replacement for documentation

I feel like they are too focused. And not having to go through the docs to find the piece I'm searching for results in me missing out on important context / possibly even better ways to solve my problem.

Re: Zed AI

#298
post #91

If I just use nvim and my own AI plugin ecosystem, is Zed AI worth trying? https://github.com/jackMort/ChatGPT.nvim https://github.com/olimorris/codecompanion.nvim https://github.com/Robitx/gp.nvim https://github.com/frankroeder/parrot.nvim

Do you use all of these at the same time? If you'd pick just one or two: Which and why?

Re: Zed AI

#299

Has any long-term Emacs user delved into Zed and ported the cool features yet? Don't take it as sarcasm, I am genuinely interested. I think Emacs' malleability is what still keeps it alive.

Long-term Emacs user here: I actually just switched entirely to Zed.

What made you switch?
Post reply on HN