4 ms·
For those that have used Vim/Neovim, Kakoune, Helix and other terminal editors, which one is your favorite? I use VSCode and have been looking to switch, I use
by satvikpendem 3y ago
For those that have used Vim/Neovim, Kakoune, Helix and other terminal editors, which one is your favorite? I use VSCode and have been looking to switch, I use Neovim inside VSCode (without the emulation of something like VSCodeVim) [0] which is decent but that's mainly because I don't want to set up all the plugins for Neovim again. Helix seems interesting because most things are built like with VSCode, it just works™, but I have to learn a new keyboard control scheme.
[0] https://github.com/vscode-neovim/vscode-neovim https://github.com/vscode-neovim/vscode-neovim
- haolez 3y agoI think the biggest benefit of going away from something like VSCode or IDEA is frictionless creation and integration of new tools. VSCode and IDEA usually require you to write plugins to achieve a deep level of customization for your needs, which causes a lot of friction. In an environment like Vim and Emacs, you can make quick scripts that create new features for your project that you wouldn't have created otherwise. I'm currently using VSCode, but I don't code a lot these days. If you are looking to explore a new paradigm like that, I would go with Emacs as a practical option (with vi bindings) and Acme as a way to open your mind (but not very practical).
- satvikpendem 3y agoTrue, that is a benefit, but realistically though, I probably won't be writing any scripts or plugins myself for the editor I use, same as with VSCode, I just get them from others or on the Extension Marketplace.
- kaba0 3y agoHow is this different than writing a plugin?
- SushiHippie 3y agoIMO learning the helix keybindings is definitely worth it. Install it, check with `hx --health` what LSPs you need and install these and that's it. And you still have so much configuration you could do, but don't really need.
- satvikpendem 3y agoThere is still no plugin support for Helix though right? That's what keeps bringing me back to VSCode, there is always something missing in each editor I look at. Same for VSCode though to be fair, it's sometimes slow on large files and especially when doing type checking, but it's a trade-off I'm making for its DX, I suppose.
- dkarl 3y agoI like that Helix's approach is different, and I think the lack of plugins is essential for it to remain on its chosen path. If Helix got plugins, then soon enough everybody would be scratching all their itches using plugins, there would be no users for the core functionality, and it would be the same kind of ecosystem we already have for emacs and Neovim. What would be ideal for me, but probably not possible in reality, is an editor that cannibalizes popular plugins. So, if a feature is sorely lacking, the plugins appear, but eventually the core functionality grows to replace the plugins. A new user installs the editor and gets a rich set of features that are battle-tested and built to work together. What seems to happen in practice with emacs and Neovim is that the core never gets any bigger, so a new user gets zero benefit from those decades of work, experimentation, and discovery, until they invest the time to integrate dozens of disparate packages into their own setup which they will have to maintain themselves over time.
- eviks 3y agoBut that seems to happen in practice with emacs and vim, why would the newly designed editors follow the same rotten path, after all they've managed to break some significant conventions of those other editors? The other "in practice" side is that without plugins the editor will never get as good as a properly (though painfully, though less painfully with some preconfigured distribution) configured alternative one with plugins
- wrapperup 3y agoI've used all except Kakoune. For me, Neovim is the one that stuck. Helix is cool, but having no plugins is a deal breaker (for now!) The onboarding experience is much nicer for sure, and Helix's LSP is way easier to set up than Neovim's. That being said, Neovim, once you get it set up, is great. The biggest hurdle for me was the config, but if you just start from scratch and make a light config (mines about 200-300 lines, with LSP, hints, etc) you can get through it. And you never have to touch it again, since most likely you configured it in a way you like. Well unless you wanna add the occasional plugin. There are also distros of Neovim that contain a fully baked IDE-lite experience, but honestly those have extremely complicated config, and often IME don't feel nice and light. It's definitely not for everyone. There is that time investment to get started, but it's definitely been worth it for me. My config: https://github.com/wrapperup/nvim-config https://github.com/wrapperup/nvim-config
- satvikpendem 3y ago> And you never have to touch it again, since most likely you configured it in a way you like. That was the issue for me, there actually is quite a bit of churn in the Neovim plugins ecosystem compared to VSCode (Packer vs Lazy for plugin management is just the latest iteration). I used to have Neovim plugins all built out but the churn was too much for me.
- wrapperup 3y agoOh yeah for sure. I haven't had that happen to me, but when I dropped AstroNvim, I had a chance to start from fresh (on lazy). Small customized config also means smaller and more precise changes. I haven't touched mine in quite a long time, only usually to add that cool trick or plugin that pops up every so often.
- lawn 3y agoI think it's what you do with it. I've used vim-plug for over a decade and it's been working fine. Yes there has been a lot of churn within some plugins, but overall it hasn't been that bad in my opinion. And with lazy tracking plugin versions in a lock file, it's easy enough to pin plugins to a known good version whenever something breaks. (I finally rewrote my entire config, and lazy is vastly better than vim-plug. I should've done so sooner.)
- bern4444 3y agoI use NeoVim. I used Vim previously and just know the built in basics very well. NeoVim incorporating Lua as a first class language has allowed plugin authors to build plugins that are faster and better than plugins for Vim written in VimScript (or other languages like python/typescript which are much slower). There is a strong community for neovim on reddit, youtube, etc and plugin authors do a nice job of building tools that work with each other. Setting it up I agree is a pain, but once done its very little maintenance/work. Even when I've had to 'redo' my setup (eg switching package managers like vim plug to packer to lazy) its been easy and under 15 or so minutes. I edit minor things in my config every few months. Everything flows quite nicely now and breaking changes are far less common than they used to be (at least among the plugins I use). My vim config if you're curious (along with the rest of my dotfiles): https://github.com/sbernheim4/dotfiles/tree/master/vim https://github.com/sbernheim4/dotfiles/tree/master/vim
- dkarl 3y agoI haven't used Kakoune, but I've used emacs, Neovim, and Helix. I love the simplicity of Helix and how easy it is to get it up and running with language servers. Emacs and Neovim have amazing ecosystems, but I'm not willing to devote the time needed to keep my setup working and do the labor of installing and configuring so many plugins. I actually switched from emacs to a mix of VSCode and JetBrains IDEs (PyCharm, DataGrip) but I sometimes find myself copy-pasting blocks of text into emacs when I need to do anything fancy or repetitive. I used a Neovim integration for VSCode for a while but found it annoyingly buggy. IDEs like VSCode and JetBrains seem to be in denial about coding being a text editing activity. Emacs and Neovim want you to take on a part-time job building and maintaining your own personal editor application out of a pile of spare parts. Helix to me is a very promising approach: a text editor that aspires to provide enough polished core features to be a productive coding environment.
- broscillator 3y agoFWIW it took effort for me to choose and curate my nvim plugins, but there's almost 0 time and effort invested in maintaining it. Occasionally CoC will ask me to update it, that's running a single command. That's it, as long as you're not constantly looking for new tools and plugins (we've all been there), once you settle on your setup, there is no maintenance whatsoever.
- ilc 3y agoI've used NeoVim, I was a long time emacs user in the 90's. Etc. Honestly: I use Jetbrains IDEs now. It is worth having the little integrated tools, like the debugger, etc. I have a nice NeoVim setup but it gets used less and less now.
- hiAndrewQuinn 3y agoHelix is very cool, and I liked playing around with it. But it doesn't support Copilot, which is an instant deal killer for a lot of people, myself included. I'm sticking with Neovim, especially because I work close to a lot of embedded stuff where being handy with stock vim comes in handy quite frequently.
- klardotsh 3y ago"For a lot of people"? I'm not saying your experience is invalid, I'm just curious how big the overlap of Codepilot users and potential Helix users is. I don't know anyone personally who likes Codepilot, and only a few who have used it at all. To me it still seems to be a niche (and probably copyright law violating) product.
- 59nadir 3y agoProbably a lot of people, yeah. More than half of the developers I know use Copilot. The vast majority of those that do use it are (Neo)vim users, which should have plenty of overlap with Helix. Also, I don't know what there is to like about Copilot. It fills in code based on what's around it more or less matching intent. It's basically a tool to fill in pieces that someone was going to write anyway, as far as I'm concerned.
- hn92726819 3y agoI have used all three. Vim for ~5 years, then kakoune for 2 years, then helix for 2 months, and back to kak for 2 years (with no end in sight). Kakoune is my favorite and helix is very nice, and I would never go back to vim. Vim: + ecosystem is nice. Plugins and matching keybinds in ACE/codemirror/whatever was cool for interop + having vi or vim on any Linux box is nice - you have to have plugins for basic things like pcre, correct colors (csapprox), and ale - at least when I stopped using vim, the multiple cursors plugin was nothing near as good as the other two. It was tacked on to a single-cursor editor, and you can tell Hx (my knowledge is 1-2 years old): + felt completely natural coming from vim. If you use vim and don't want to warp your brain with new keybinds, try hx. It feels like vim+more. Kak feels like a different editor + many built-in features that require plugins in vim/kak + using LSP motions felt amazing + written in rust, which I love. The codebase is entirely readable and I contributed a patch after only about an hour first looking at it - hx didn't have motions for ()/<>/... Which I've come to rely on. Kak has m which is like Vim's f(v% if f was multiline - no advanced keybinds/bindsym in vim/map in kak. Config was toml so the most you could do was bind single chars to other single chars - no plugin support, though I found myself not really longing for any plugins because so much comes by default - occasional crashes due to off-by-one errors and .unwraps sprinkled around Kak: + editing feels amazing. Like the text is directly connected to your brain. This is because basically every action gives you feedback. For example, in vim, t(dt) gives you a cursor move and then the text is gone. t(v%d gives you feedback but takes way more keys, but in kak, md immediately selects the entire bracket after m and deletes it after d. Having visual feedback *as a requirement* (not an option like Vim's visual mode) is amazing. I didn't use hx enough to know if it feels like vim or kak in this regard + plugins exist. Kak-lsp is nice. Scripting your own keybinds feels more natural because the scripting language *is* the keybinds, contrary to vim. Basically imagine every keybind is like Vim's but with a :normal before it + multisel feels compltetly natural. Not like an extension to what you're doing, but everything is multisel, and you just happen to have n=1 selection sometimes +/- piping to external programs feels very natural. I have numerous scripts that take stdin and write to stout. In kak, I select whatever I want and just run |encode-url<ret> and it pipes every individual selection to my command and replaces them with my output. This is also bad because if I have 100 selections (not uncommon), it will spawn 100 shells to spawn my command 100 times - people keep saying it doesnt have a scripting language, which is misleading IMO. There are try blocks, %{} groups, and commands that you need to learn about. Look at hx if you're interesting in no scripting language. It reads a toml config file and that's it. - a little overreliance on shell. I don't even know if windows can run kak because it uses shell so much. On one hand it's nice because I know Shell. On the other hand, interop feels weird. You echo commands and kak reads your stdout and evaluates it. It's clever and cool, but something about it feels weird. - keybinds don't behavibe like vim or hx. You have to retrain your muscle memory, but IMO it's worth it. Using vim now though is painful Kak is great
- dpc_01234 3y agoI was using Kakoune for 3-4 years, and switched a year ago to Helix. Kakoune is OK, but: Some details of editing are too optimized for counting keystrokes in vim golf, less for thinking-free editing experience. Configuring and extending text editor with shell scripts is ridiculous. It's in C++. I want to be able to debug and submit changes to my most used dev tool and I don't want to be touching C++. Having said that, I still miss the visual-mode-first experience of Kakoune (most moves in Kakoune change/modify selection, while Vim/Helix have visual mode instead). Otherwise I think Helix already leaped over Kakoune in terms of functionality and polish, because it's just easier to contribute to (in Rust). BTW. The difference between Vim and Kakoune/Helix is not that big. For basic Vim modes in shells and other tools, I don't really notice it. `hjkl` works all the same.
- BaculumMeumEst 3y agoAgreed on all points. And one more issue with Kakoune: while delegating all windowing functionality to the terminal emulator probably sounds great to the editor implementer, for a user it is fucking annoying. An editor should be able to manage splits and tabs. It should have a basic concept of some kind of UI pop ups. Kakoune can feel _amazing_ to use at times, but it is at the same time a case study on why brutalist minimalism isn't the best design goal.
- xcdzvyn 3y agoCould I ask what Vim can do that Kakoune + Tmux can't? I don't doubt there's something, I've just never encountered it.
- BaculumMeumEst 3y agoI mean you definitely can manage splits and tabs and even pop up ui with tmux, just like you can extend kakoune by writing shell scripts with kakoune’s eldrich horror nesting of editor contexts. I just think both of those things are a huge pain in the ass to deal with.
- jacknews 3y ago
- Hammershaft 3y agoHelix is easier to jump into as it supports a lot of useful code editing features out of the box, but Kakoune has a more elegant and discoverable modal editing experience.
- 59nadir 3y agoKakoune is also possible to use not as the creator intended or foresaw, which Helix isn't. If someone has any tinkerer in them at all Helix will be an awful editor to use as they'll probably spot some thing they want or need and be unable to add it.
- broscillator 3y agonvim. There isn't much software I can say that feels so comfortable to use for me. A lot of people look at the learning curve and decide it's not worth the time investment, just so they can save time later on when they're more comfortable with it. But to me it's not about time, it's about how smooth it feels to use, how I can translate thinking to typing/editing with the least friction possible, and nvim with my minimal set of plugins that I curated over years, that is it.
- oira-oira 3y agovis