Mission statement

[z3t0]

Project VimR is an attempt to refine the Neovim experience (or it is just YA Neovim GUI for mac OS). The goal is to build an editor that uses Neovim inside with many of the convenience GUI features similar to those present in modern editors. We mainly use Swift, but also use Objective-C when its C-nature helps

It would be valuable to those interested in contributing what makes this different from other GUIs, especially since other efforts are cross platform in comparison.

[romaninsh]

I can explain why I stuck with VimR. I may not be 100% correct on some of the points, but those are still my reasons nonetheless.

• it's really snappy. Very fast start-up. No interface lag. Very stable. Minimal CPU usage.
• it does not try to copy IDEs or Atom, very close experience to 'neovim' in the terminal.
• it tries to compliment neovim features not reinvent them, so as NeoVim introduces more UI stuff, it probably would be available in VimR but not sooner.

So the choice to use Swift for maximum performance is something I really appreciate. I wouldn't benefit from using cross-platform foundation, but for me, it's very important that my not-so-powerful MacBook Air navigates files quickly while I'm screen sharing and recording my screen off the 4K display.

Perhaps the original ambition was to add more features and compete with modern editors, but that's a very ambitious goal.

I would say that: "VimR brings NeoVim as a native application for Mac OSX with the focus on speed, stability, efficiency and seamless integration with the operating system. The shell application is written mostly in Swift and will work with no extra configuration.", probably would describe the current state of VimR better.

[qvacua]

@romaninsh thank you for the nice summary. With the latest scroll performance improvent (still with an open issue GH-472) VimR has become very fast :)

I'll try to write some lines here in the next days.