Hacker News new | past | comments | ask | show | jobs | submit login

>Speak for yourself, those are why I supported OniVim.

Why are you so obsessed with this subjectiveness? I'm just saying that speed and vim-like editing where not a selling point. Because you can already have those in VSCode with neovim backing it up. Not to mention you could've already have speed and vim-like editing via projects like VimR (tens of them out there).

>The GUI was not what was important to me

>I thought OniVim would bring that^1 but it seems it is not anymore.

You are contradicting yourself here.

[^1]: "(neo)vim plugin installation still isn't as easy to work with as a one click package / language server install like in VSCode."




On the contrary, I think it is you who is obsessed with what I should or shouldn't think of as a selling point. I used to use VSCode, it was slow, I found OniVim and it was fast, why is that so hard for you to accept as the reason I liked and bought the application? As I said, speak for yourself, if speed wasn't a consideration then good for you, for others it is.

Regarding the plugin support, there is no contradiction. Rather than the words "one click" however, which brings to mind a GUI, I should have said Neovim has a more annoying plugin story (through packer which has a lot of configuration) than VSCode or OniVim, yet it is not the GUI that makes it so. If I could write in init.nvim "Plug TypeScript" just as in VSCode I could click "install" on the TypeScript extension, those are both equivalent to me, even as the latter is GUI based while for former is terminal based.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: