←back to thread

301 points nogajun | 1 comments | | HN request time: 0s | source
Show context
tiffanyh ◴[] No.45941935[source]
I was always bummed OniVim v2 didn't take off.

It was a native IDE but fully supported VS Code plugin system.

https://web.archive.org/web/20210627210456/https://v2.onivim...

replies(2): >>45943097 #>>45943304 #
koiueo ◴[] No.45943304[source]
From a quick glance, I can't understand the target audience.

Vim users would be annoyed by bizarre input lag of an electron application and perhaps by EULA. VS code users don't really care about Vim...

replies(2): >>45943434 #>>45960270 #
forgotpwd16 ◴[] No.45943434[source]
>of an electron application

It isn't an Electron application*, that's why GP said native. The EULA part though was probably a block to adoption.

*It uses Revery, a, made by OniVim's devs, cross-platform GUI framework (similar to Flutter but build on Reason/OCaml).

replies(1): >>45944218 #
koiueo ◴[] No.45944218[source]
Oh, ok, now I'm curious to try it despite EULA (although these days the wide choice of (neo)vim distributions utilizing LSP makes their offering less appealing). Thanks for the clarification.

The site doesn't stress the not-electron part enough, maybe that contributed to the failure.

replies(1): >>45946071 #
1. forgotpwd16 ◴[] No.45946071{3}[source]
Should've probably mentioned it before but it actually used a dual-license model by having an MIT version that lagged behind upstream for 18 months (could be found in oni2-mit repo). During last month when development stopped it was fully re-licensed under MIT (hence oni2-mit repo no longer exists).