How can I help?

[samholmes]

I've occasionally been checking into this project to keep an eye on its progress. Looks like the development has slowed down a bit, which is unfortunate. Does this project need more developer resources, or funds? I'd be happy to pay for the product once it's out of alpha and the kinds have been ironed out and I could replace VS Code with Onivim2. Is the project still on track?

[kinglouie]

unfortunately this project is dead atm, see #3811

[samholmes]

Rather than call it dead, why not open it up to the community to develop? Seems reasonable to go fully open source with it. @bryphe What say you?

I have been increasingly interested in modal editing and now am using vim-mode in vscode, but it doesn't quite cut the cheese. I've been becoming interested in projects like kakoune and helix as an alternative to modal editing style. Onivim 2 has always appears promising to be the ideal editing experiences once all the vscode features had come to the platform (like debugging etc), so I kept it in the back of my mind.

I'd be motivated to be apart of the next step in Oni2's history. I have this thought, what if it wasn't just a vim-modal editor, but instead fully agnostic to which modal editor library you choose to use. By default, libvim perhaps, but I imagine a libkakoune or a libhelix could broaden the user-base and use of a post-modern IDE/code-editor. We could call this new version Onix; It's Onivim, onikakoune, onihelix, etc. The X is for extensible, the promise is to maintain a flexibility for all modal editors alike, and be the platform and ecosystem for modal coders.

Alternatively, Onix could just be the Helix variant of Onivim, but I am all for supporting more user bases. I personally like Helix for its design chooses and performance. Having a helix modal editor combined with all the extra vscode features would make for a very unique value proposition in the IDE market.

Thanks for listening. I hope this project comes back to live in a very wonderful way.

Cheers!

[CrossR]

Rather than call it dead, why not open it up to the community to develop? Seems reasonable to go fully open source with it. @bryphe What say you?

We lack a proper formal announcement, but Oni2 is fully open source now since 9f36dab.

Having a more agnostic backend would be difficult, but would unlock a bunch of different interesting use cases. Unfortunately, the timing ended up that as Bryan was winding down, I hit the point in my PhD where I'm writing up so have basically no time to work either. But since the code is open source now, there is the ability for anyone else to fork / work on it etc.