Hacker News Reader

Comment by msoad | Hacker News Reader

This should've been done in VSCode. Most developers don't want to write code in a browser. Once VSCode extension is built they could generalize it to other editors.

I'm sure they are thinking of VSCode integration and I am hopping for that to be available soon

View on HN

I wonder if AI tools is going to kill editor diversity. Every one of these tools VS Code is the first class citizen and other editors are an afterthought. Sure people can write their own Emacs package but that's only if the tool developers enable it and the experience is usually not as good as the official VS Code version. I can also see the future where not using VS Code is a signal you are less reliant on AI tools to code

A thousands of small cuts, almost everything comes first to VSCode before other editors, even mainstream things are underrepresented in most other editors (Jupyter, commercial integrations, etc…).

Although that was true about Atom too though?

We used to say the same about Eclipse!

This is a great fear of mine as a (neo)vim user. I've repeatedly encountered situations already where it was assumed everyone was using VS code, and I only see that getting worse as more and more integrations get built into IDEs.

There are lots of hackers bringing VsCode-only extensions to Neovim. I brought Copilot Chat to neovim back when it first became available to me and the community is still alive and well, though with a different maintainer. Tbh AI tools aren’t that useful, and those that are will get ported. Currently trying to bring Cursor to Neovim but that has proven much more difficult

I don't know that I can say thank you enough for your work! Thank you!!!

Do you know why Github didn't make an official version? I'm definitely going to give yours a try, and I don't really care whether it's "official" or not, but rather I'm curious because looking for official neovim support is a useful signal of their priorities/intentions.

Link btw since it’s on a org: https://github.com/CopilotC-Nvim/CopilotChat.nvim

Re: official version

There was some discussion but the answer is that it’s just too difficult. Our version was reversed from a bunch of MITM and guesswork. The VSCode implementation has a “@workspace” command which involves complex tree-sitter integration, sending off all your code to be vectorized, and uses RAG to get the most relevant snippets. We obviously weren’t able to implement all features. They can get away with this in JavaScript because you can get just about anything via npm. In Lua, most things have to be from scratch. I had to spend a few hours just getting tiktoken working in Lua and even then it requires manual installation. The package management system with Lazy.nvim is very lacking.

Thank you! I'll be trying this out in the next few days as soon as I get some time. I much appreciate your effort. I know you don't do it for the money, but I'll throw some sponsor bucks your way. I'd love to buy you a few beers (or coffees or whatever your love is) :-)

I'm still chugging along on sublime text 3

We are indeed thinking about how to do that in a way that feels natural in VS Code. :)

But, VSCode is in a browser?

https://vscode.dev/

It's very different to have the code and suggest things than it is to obtain the code and suggest things, without introducing noticeable delay in processing that code

Reply on news.ycombinator.com