3 ms·

It says it's powered by React and (presumable) Electron - does it have the same kind of issues that Atom does? Can it open big files, how responsive is it, etc.

by chc4 9y ago

It says it's powered by React and (presumable) Electron - does it have the same kind of issues that Atom does? Can it open big files, how responsive is it, etc. How do plugins work? Do neovim plugins work out of the box with Oni, do you have to write a wrapper, or are they completely incompatible? This is really the make or break part of it.

bringtheaction 9y ago
> Can it open big files Yes it should be able to do that. Neovim runs separately from frontends like the one in the OP. https://github.com/neovim/neovim/wiki/Plugin-UI-architecture https://github.com/neovim/neovim/wiki/Plugin-UI-architecture
- deleted 9y ago
  [deleted]
pault 9y ago
By default it doesn't load your init.vim, but if you change that flag in the config it will behave exactly like your regular neovim install (since that is in fact exactly what it is: a very light canvas renderer wrapped around neovim). I have been using it for a couple of weeks with all of my vim plugins with no issues (ctrl-p, buffer gator, easy motion, etc). Edit: it's worth pointing out that while the rendering is done with electron/canvas, everything else is delegated to neovim. I haven't noticed any slowdown with 1000+ line files, but if you're talking tens of thousands... maybe.
- jimnotgym 9y ago
  I don't have any problem with 1000 line files in Atom either. It sucks at 100,000 line files, but I only ever open them in an editor by accident (Atom gives a warning). That is what grep and tail are for
bryphe 9y ago
If you're comparing Oni to Atom, the architecture is actually quite different. Oni uses Neovim at the core to manage buffers & buffer manipulation (in other words, a native layer vs JavaScript in Atom) - this is a major benefit when working with large files. In addition, Oni uses a canvas renderer for the editor surface vs the DOM used by Atom. Together, these significantly improve the responsiveness of the tool. Architecturally, Oni is more similiar to the Xray project being investigated by the GitHub team: https://github.com/atom/xray https://github.com/atom/xray. Most neovim plugins work great with Oni :) Just set the `oni.loadInitVim` configuration value to `true`: https://github.com/onivim/oni/wiki/Configuration#oni https://github.com/onivim/oni/wiki/Configuration#oni
deleted 9y ago
[deleted]
thickjgoat 9y ago
The latency and memory usage is arguably far worse than Atom but that would be expected given its infantile state.

by chc4 9y ago

bringtheaction 9y ago

> Can it open big files Yes it should be able to do that. Neovim runs separately from frontends like the one in the OP. https://github.com/neovim/neovim/wiki/Plugin-UI-architecture https://github.com/neovim/neovim/wiki/Plugin-UI-architecture

deleted 9y ago
[deleted]

pault 9y ago

By default it doesn't load your init.vim, but if you change that flag in the config it will behave exactly like your regular neovim install (since that is in fact exactly what it is: a very light canvas renderer wrapped around neovim). I have been using it for a couple of weeks with all of my vim plugins with no issues (ctrl-p, buffer gator, easy motion, etc). Edit: it's worth pointing out that while the rendering is done with electron/canvas, everything else is delegated to neovim. I haven't noticed any slowdown with 1000+ line files, but if you're talking tens of thousands... maybe.

jimnotgym 9y ago
I don't have any problem with 1000 line files in Atom either. It sucks at 100,000 line files, but I only ever open them in an editor by accident (Atom gives a warning). That is what grep and tail are for

bryphe 9y ago

If you're comparing Oni to Atom, the architecture is actually quite different. Oni uses Neovim at the core to manage buffers & buffer manipulation (in other words, a native layer vs JavaScript in Atom) - this is a major benefit when working with large files. In addition, Oni uses a canvas renderer for the editor surface vs the DOM used by Atom. Together, these significantly improve the responsiveness of the tool. Architecturally, Oni is more similiar to the Xray project being investigated by the GitHub team: https://github.com/atom/xray https://github.com/atom/xray. Most neovim plugins work great with Oni :) Just set the `oni.loadInitVim` configuration value to `true`: https://github.com/onivim/oni/wiki/Configuration#oni https://github.com/onivim/oni/wiki/Configuration#oni

deleted 9y ago

[deleted]

thickjgoat 9y ago

The latency and memory usage is arguably far worse than Atom but that would be expected given its infantile state.