3 ms·
It seems neat, though I would never seriously use an editor that I couldn't run in a terminal. Too much of my work happens remotely. Additionally, in my mind a
by okasaki 5y ago
It seems neat, though I would never seriously use an editor that I couldn't run in a terminal. Too much of my work happens remotely.
Additionally, in my mind a terminal serves a similar role as plain HTML web pages - it constrains what can be done and I am extremely used to it, which makes it very easy and quick to use. On the other hand in a GUI editor (or a JS-heavy web page) it feels that it has more possibilities, which allows authors to customize things in ways that I don't expect, which can take away from my focus on what I'm doing. There's also the additional curse that because of these possibilities, authors seem eager to change things more often, whereas I value stability.
- Santosh83 5y agoIsn't this just a UI layer for NeoVim, which you can easily switch to text when going remote?
- hinach4n 5y agoIt is, OP is overreacting. This is just a front end. I'm pretty sure it just uses the neovim binary on your system in headless mode.
- cycomanic 5y agoThese are all valid points, but I don't think they apply here. This is a GUI frontend for Neovim, which is a terminal editor. So yes you can use the the editor in the terminal. This just gives you the option to run the same editor in a GUI for when you need it.
- jcelerier 5y ago> Too much of my work happens remotely. ... You know that GUI apps are able to edit code over SSH too, right ?
- erikbye 5y agoExactly. Jeez. I'm not even shocked anymore, at how out of touch and stuck in their ways some people are. If this is your workflow: terminal; ssh <remote server>; vim <file> ...
- ncmncm 5y agoI have been using sshfs to give local editors access to remote files. Are you suggesting a better way?