4 ms·

How can it be a successor to Oni if it's terminal-only application?

by konart 4y ago

cercatrova 4y ago
Due to speed and vim-like editing, with certain things like tree-sitter support built in, similar to how Oni has things built in. With (Neo)Vim you'd have to configure that yourself. That it's terminal versus GUI doesn't make much difference to me, since as long as it shows text/code on the screen, I don't really care how it displays it.
- N-Krause 4y ago
  OniVim's main selling points was it beeing close to VSCode, so saying Helix Editor is its successor but not having the main features does not make a lot of sense to me. Based on your points it sounds like Helix Editor is pretty much the same as SpaceVim.
  - cercatrova 4y ago
    I used OniVim due primarily to speed and not having to set up a vimrc. That it was a GUI app versus terminal based is immaterial to me. Now I have my own vimrc so it doesn't matter much anymore, but last year OniVim was nice enough to use.
- konart 4y ago
  As stated already - the main selling point of Oni is\was VSCode-like UI, ease of extension installation etc. Speed or vim-like editing was not a selling point at all. >I doesn't make much difference to me Okay, but this is completely beyond the point.
  - cercatrova 4y ago
    > Speed or vim-like editing was not a selling point at all. Speak for yourself, those are why I supported OniVim. The GUI was not what was important to me, it was the ability to install extensions easily, have vim keybindings, and most importantly, be able to handle the very large files I often work with (due to being written in OCaml), where VSCode hangs.
    - andreypopp 4y ago
      To be honest it seems vim/neovim ticks all those points already.
      - cercatrova 4y ago
        Yes, however (neo)vim plugin installation still isn't as easy to work with as a one click package / language server install like in VSCode. I thought OniVim would bring that but it seems it is not anymore.
    - konart 4y ago
      >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."
      - cercatrova 4y ago
        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.

How can it be a successor to Oni if it's terminal-only application?

by konart 4y ago

How can it be a successor to Oni if it's terminal-only application?

Due to speed and vim-like editing, with certain things like tree-sitter support built in, similar to how Oni has things built in. With (Neo)Vim you'd have to configure that yourself. That it's terminal versus GUI doesn't make much difference to me, since as long as it shows text/code on the screen, I don't really care how it displays it.

N-Krause 4y ago
OniVim's main selling points was it beeing close to VSCode, so saying Helix Editor is its successor but not having the main features does not make a lot of sense to me. Based on your points it sounds like Helix Editor is pretty much the same as SpaceVim.
- cercatrova 4y ago
  I used OniVim due primarily to speed and not having to set up a vimrc. That it was a GUI app versus terminal based is immaterial to me. Now I have my own vimrc so it doesn't matter much anymore, but last year OniVim was nice enough to use.
konart 4y ago
As stated already - the main selling point of Oni is\was VSCode-like UI, ease of extension installation etc. Speed or vim-like editing was not a selling point at all. >I doesn't make much difference to me Okay, but this is completely beyond the point.
- cercatrova 4y ago
  > Speed or vim-like editing was not a selling point at all. Speak for yourself, those are why I supported OniVim. The GUI was not what was important to me, it was the ability to install extensions easily, have vim keybindings, and most importantly, be able to handle the very large files I often work with (due to being written in OCaml), where VSCode hangs.
  - andreypopp 4y ago
    To be honest it seems vim/neovim ticks all those points already.
    - cercatrova 4y ago
      Yes, however (neo)vim plugin installation still isn't as easy to work with as a one click package / language server install like in VSCode. I thought OniVim would bring that but it seems it is not anymore.
  - konart 4y ago
    >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."
    - cercatrova 4y ago
      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.