11–20 of 136 posts
How fast does this feel compared to VS Code? I went into the whole onivim -> revery -> reason rabbit hole and the native code compilation is compelling, but Flutter does the same thing and is pretty slow.
Isn’t this VS Code with the Vim extension?
No, likely out of diffidence onivim has a very similar design to VSC. It doesn't appear to share any code with VS Code though.
But the actual core editor is all seperate, written in ReasonML (or OCaml if you know that instead), with a bunch of C libs in the background we've wrapped (Skia/Harfbuzz/We wrap real vim etc).
So the core editing experience has no code sharing, but the extension side of things does!
Buying software without a trial makes me disinterested. I still want to learn using vim every day, but won't commit to this text editor/vsx-powered IDE, unless I find out that I have the guts to use it every day. Also, there is VIM mode for VS Code, I guess.
Partially that is a thank you to those who have supported our development, and partially its to help put up a small barrier to entry, just so we don't get too flooded with issues and feature requests!
A public release is coming soon-ish, and can be used for non-commercial use.
Buying software without a trial makes me disinterested. I still want to learn using vim every day, but won't commit to this text editor/vsx-powered IDE, unless I find out that I have the guts to use it every day. Also, there is VIM mode for VS Code, I guess.
> Also, there is VIM mode for VS Code, I guess. I feel like this is something said by people who are more invested in VS Code than vim. The main vim plugin for VS Code is straight trash.* It's slow, buggy, and unintuitive; while lacking the extensibility that vim has. At least IDEAVim, which has the same limitations of being built in another IDE, replicates enough of the common plugins to be pleasant. It's also worth…
We skipped that and haven't implemented any vim backend at all!
We use/made libvim[1], which is just the vim source, that we've essentially turned into a library. So its the vim code base with terminal UI stuff stripped out, and an interface added for us to hook into it. The README of that repo has some good insight into that (including why we didn't use neovim here, as much as the team all loves nvim).
We don't support vimscript stuff at the moment, but its in progress as all the vim source code is there to load/run it as normal, its just about integrating is properly into Oni2 (making sure keybinds are working, commands are properly loaded, packing stuff up nicely for distrib etc).
(There is some other motivation bits in this doc[2]. Its outdated since we haven't edited it since before the project started, but it outlines the motivations we went in with etc).
[1]: https://github.com/onivim/libvim [2]: https://github.com/onivim/oni2/blob/master/docs/MOTIVATION.m...
I stared at the landing page for a good 15 seconds wondering "why is that picture... breathing?"
[1]: https://github.com/VSCodium/vscodium/issues/196#issuecomment...
Isn’t this VS Code with the Vim extension?
Yes, it's not using native widgets (so no built-in accessibility), but that might be fine in many cases.