5 ms·
> If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ https://helix-editor.c
by yjftsjthsd-h 4y ago
> If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ https://helix-editor.com/, or new native GUI editors like https://zed.dev/ https://zed.dev/ ?
VS Code is a proprietary, spyware-riddled, resource-wasting worked example of why "modern" software sucks. Also for my personal use, everything that's not vim suffers from being not vim; it would cost me effort to switch for no clear benefit, and I'd still need to retrofit the same control scheme into whatever it was because the muscle memory is too strong, at which point I might as well just use actual neo/vim.
> which were built to be used as rich development environments instead of extensible text editors
> spent months tweaking Neovim/Emacs configs
I think part of the difference might be of usecase; if you want an IDE, use an IDE. If you needed to spend that much time bending the tool to what you want, maybe it wasn't a good tool to use. When I open vim, it's because I want a text editor, and it provides a text editor.
- cercatrova 4y agoI use VSCode since switching away from Neo/Vim because things just work. I don't have to install a bunch of plugins like I used to where I don't know what works and what doesn't work with each other. For example, for Rust, I go to VSCode extensions page, click install on rust-analyzer, and that's it. I don't have to set up an LSP, syntax highlighting, etc which are each their own plugin on Vim.
- justinpombrio 4y agoThat's funny, I just switched from VSC to NeoVim because things just work. The C++ LSP bindings for Vim were easier to set up, faster, and more reliable than my setup in VSC. Though I imagine these things vary greatly, since C++ and C++ tooling is enormously complex and varies from codebase to codebase.
- ii41 4y agoI just want to express why I sometimes prefer things that don't "just work". I love VSCode. I use (neo)vim just because I am used to them (started using them before VSCode was around). Firstly, not "just work" means there will be no features to suddenly appear and "help" me. When I start to use a new IDE I never know what inserting "{" does: Will a "}" also appear? Will it start a new line? Will it cause indentation to change? Will it insert a whole snippet? How do I just insert a "{"? An IDE usually comes with lots of "helper" features like this, and questions like these add up. The result is that I never know what happens when I press a key and get agitated when the result isn't what I expect. If I set up everything myself this doesn't happen. (neo)vim is pretty bad in this sense actually. The default formatoptions and filetype indent plugins are pretty annoying, and the "J" normal mode command has behaviors that surprise users and cannot be turned off (you can remap it for sure), but by the time I met VSCode I got familiar enough with them already... I recall VSCode's default was pretty clean. IDEs are absolutely the worst. Not "just work" also means that I know how to change something if it steps into my way, since I set up everything myself. If I have to edit a file with special formatting rules that I need to follow, I know where to change auto formatting rules. If I have to read some generated code or code from dependency libraries, I know where to turn off warnings from linting. Since rust-analyzer is set up by myself, if one day I find that its version or config is not compatible with this new project I am starting to work on, I know immediately how to change it. If my whole setting up effort is "clicking a button", it becomes harder for me to find where the change needs to be made. Such things are not just "if"s actually, but happen pretty often from my experience, often enough to make me think it's better to set up everything myself than to figure things out each time.
- d3nj4l 4y agoIf VSCode "sucks", then isn't it weird that the vast majority of people seem to love and even prefer using software that "sucks", including GP?
- yjftsjthsd-h 4y agoI'm not sure how you'd know that; since vim, emacs, and other more traditional options don't include telemetry we don't know how many people use what editors. In any event, Windows remains the most-used (desktop) OS, so I've long since acclimated to people living with the suckage.
- Winsaucerer 4y agoThere's some data here that can help give a clue: https://survey.stackoverflow.co/2022/#most-popular-technologies-new-collab-tools https://survey.stackoverflow.co/2022/#most-popular-technolog.... It does look like vscode is the most used by a very large margin.
- yjftsjthsd-h 4y agoScrolling up, the same sample put NPM use at 65.17%, so I feel pretty comfortable calling it sample bias.
- Winsaucerer 4y agoThe data is no doubt biased, but given just how far ahead vscode is, it would need to be a very heavy bias to see vim/nvim come out ahead among all developers (however we define that). It gives us some information, but I agree doesn't tell us what the proportion is among all developers.
- bee_rider 4y agoPopularity is not a great metric of goodness, unless we want to come to terms with the fact that Limp Bizkit records are around 3x as good as VSCode (and that's despite the fact that they aren't even charging people for VSCode!)
- johnfn 4y ago> VS Code is a proprietary, spyware-riddled, resource-wasting worked example of why "modern" software sucks. Perspectives like these (and others in the thread) remind me that there exists a separate cohort of engineers from people like myself which have absolutely polar opposite views. I respect your opinions, though I couldn't disagree more with them! :) Well, except the bit about VSCode having "spyware". That's not true, and it weakens your point. It does have telemetry - I suspect that's what you mean, and you should just call it that instead.
- modernerd 4y ago> and you should just call it that instead. And then turn it off using the built-in setting: https://code.visualstudio.com/docs/getstarted/telemetry#_disable-telemetry-reporting https://code.visualstudio.com/docs/getstarted/telemetry#_dis...
- aeze 4y agoYou could also, if you wish, audit the telemetry events and determine if it's worth turning off - or decide that it's okay with you that they're using that data to improve their free product. https://code.visualstudio.com/docs/getstarted/telemetry#_viewing-all-telemetry-events https://code.visualstudio.com/docs/getstarted/telemetry#_vie... https://code.visualstudio.com/docs/getstarted/telemetry#_gdpr-and-vs-code https://code.visualstudio.com/docs/getstarted/telemetry#_gdp...
- MichaelCollins 4y agoSearching for excuses to let the company's product spy on you sounds like a huge waste of time.
- yjftsjthsd-h 4y agoI could also just decide that it's okay to use a free editor that doesn't report on me in the first place. I don't need to audit exactly what information vim sends off and evaluate whether it's too much, because "none" is really easy to decide on.
- peppermint_tea 4y agoon linux, kde/kate is pretty good... I switched back to full tmux+vim lately to get even better with vim, but I find that kate is the perfect mix between an ide and a terminal based editor. makes me think of notepad++ with a few extra goodies (files on the left, terminal below etc...)
- cassepipe 4y agoLast time I tested Kate's vim mode the g letter did not work in insert mode. Kate looks great but seems even more overwhelming to configure than Vim
- wyclif 4y agoHmmm, did some of the mappings change with this release? Now hitting CTRL-B (I do that a lot in NERDTree) gives me the "E5248: Invalid character in group name" error.