7 ms·
What does this mean for the future of editors like emacs and (neo)vim? Right now the Copilot plugin for Neovim works pretty much the same as the one for VSCode,
by valedan 3y ago
What does this mean for the future of editors like emacs and (neo)vim? Right now the Copilot plugin for Neovim works pretty much the same as the one for VSCode, but as LLMs get integrated more into IDEs and new workflows are built around them, will the old-school editors be able to keep up? I'm a little worried because I just switched from VSCode to Neovim a few months ago!
- davidkunz 3y agoIt'll be great if they'd build language servers via the language server protocol, that would be editor agnostic.
- spenczar5 3y agoGithub Copilot actually works through the language server protocol already. Document contents are sent to it and it responds with code completions.
- mzz80 3y agoNeovim already can’t keep up by itself. The future of vim won’t be as a standalone application, but as a plugin into other IDEs. The support for Neovim and VSCodeVim within VSCode greatly reduces the utility of a standalone app for anything other than edits to very small projects.
- soulofmischief 3y agovim is a text editor.
- SheinhardtWigCo 3y agoThis could be the dawn of a new day for the old-school editors. Not to start any wars here, but I could never get the hang of Vim, and that's hardly an unusual complaint. But now, free high-quality personalized "tuition" just became economically viable.
- llarsson 3y agoStuff like the Language Server shows that people are interested in making new stuff work well with our old beloved editors. I have faith.
- tmtvl 3y agoThere is a ChatGPT shell for Emacs: https://xenodium.com/chatgpt-shell-available-on-melpa/ https://xenodium.com/chatgpt-shell-available-on-melpa/