These don't usually take off because people who use vim and emacs are people who insist on customizability and aren't into all the bloat that comes with IDEs. People who want IDEs aren't interested in an editor that lives in the terminal. There is a very limited market for something like this.
LazyVim
11–20 of 537 posts
Re: LazyVim
#12Re: LazyVim
#13A bit off-topic, but I wonder how much Copilot/GPT cuts into the market share of editors like vim and emacs. I used emacs for the past few years, but I recently switched (back) to vscode because the Copilot integration is really good. There are a lot GPT integraton packages for other editors, but they don't come close to the deeper integration that vscode has. And of course, vscode will probably get priority treatmen…
As you said though.. It won't compete with 1st party love given to VSC. For example, I have no idea if "neighboring tabs" is a feature in neovim.
Re: LazyVim
#14Off topic, but does anyone know what the vim theme is in the screenshot?
Re: LazyVim
#15Off topic, but does anyone know what the vim theme is in the screenshot?
Re: LazyVim
#16A bit off-topic, but I wonder how much Copilot/GPT cuts into the market share of editors like vim and emacs. I used emacs for the past few years, but I recently switched (back) to vscode because the Copilot integration is really good. There are a lot GPT integraton packages for other editors, but they don't come close to the deeper integration that vscode has. And of course, vscode will probably get priority treatmen…
Aren’t you giving your code away to Microsoft if you use Copilot?
However, there are plugins to use LLM’s while coding with Neovim and Emacs, so, you can still use these editors for that if you want.
Re: LazyVim
#17Re: LazyVim
#18Earlier quoted context omitted.
Aren’t you giving your code away to Microsoft if you use Copilot?
Ya pretty sure using copilot only applies to personal projects. To my knowledge, you can’t use LLM’s while coding at work due to CCI. However, there are plugins to use LLM’s while coding with Neovim and Emacs, so, you can still use these editors for that if you want.
Re: LazyVim
#19Earlier quoted context omitted.
I find that any IDE-type setup in vim causes vim to lose the most important thing, speed. If your movements slow down because of too many plugins, the experience is far worse than in a normal non-modal IDE.
I really haven't experienced this. There was one time i noticed vim slow down, and that was related to a relative line number bug specific to Mac, but that was fixed a while ago. I've used many of the ide type neovim premade configs, and i use my own which has a lot going on. None seem slow to me. Guess it has been a while since I've used a vanilla config. Full ide setups in neovim don't seem slow to me, especially c…
Re: LazyVim
#20Earlier quoted context omitted.
I find that any IDE-type setup in vim causes vim to lose the most important thing, speed. If your movements slow down because of too many plugins, the experience is far worse than in a normal non-modal IDE.
What is this speed you speak of? I developed in vim for a decade, then eMacs for another decade, before finally moving to VS Code. I’ve never been as productive with vim/eMacs as I am with Code, or Visual Studio proper / XCode when I have cause to sue them.