Can't stand it, myself. Of the various Neovim macOS UIs, this is the one that is perhaps closest to MacVim, but the UI choices about having the drawers present all the time and other pieces make it both less reliable and less usable than MacVim itself.

That's the main problem with most of the neovim GUIs—they get opinionated about what a Vim GUI should be. First, foremost, and always, it must be vim in a GUI window. Second, it must have native OS keybindings and integration (clipboard, menu, etc.). Finally, it should be able to have possible extensions that work well with existing plug-ins. (I use Fern for my file tree. I don’t need a built-in file tree that is always visible.) They must, at the core, always be vim. This is why I think that Oni2 was a mistake and why it’s one of the few software packages I regret paying. I don’t want vim motion keys with VSCode extensions. I want a Vim GUI.

> Great comment, I’ll add there’s a MacVim-like GUI wrapper but for Neovim called VimR that i really like.

Thanks for pointing this out. One thing I like is being able to command tab in MacOS -- if you have multiple terminal windows it breaks that, so any kind of GUI wrapper, even if it's basically just a glorified replication of the terminal app, is useful from a usability perspective. (To me at least)

That's how I originally moved from vim to MacVim -- I wanted terminal for sysadmin stuff, something like Sublime for coding, TexMaker for LaTeX (because it's it's own beast), and so on and so forth.

There's also Neovide which is written in Rust, which makes it, well, blazingly fast.

https://github.com/neovide/neovide