Onivim 2: Re-Architecting for Performance
summary
Onivim v1 uses Electron with a TypeScript/React stack and struggles with multi‑second startup and janky responsiveness; v2 re‑architects to ReasonML with a native Revery UI, a native Revery front-end, and a libvim synchronous API so keypress→render is blocking. Measured results show startup dropping from about five seconds to roughly half second startup, much lower memory use, and snappier interaction while still hosting VS Code extensions via a background process.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:54Overview
- 2:50Onivim V1
- 10:01Performance Challenge #2 Responsiveness
- 11:17V1 Performance Work
- 14:03V1 Architecture
- 15:59Ideal Architecture
- 17:18Reason
- 19:10Revery: Minimal App
- 19:47Revery: Examples
- 20:20V2 Architecture
related talks
20mVite - The Next Generation Frontend Tooling
38mHow vite changes the game for Vue and Web development
31m(Neo)Vim in 2024
15mVite: The next generation frontend tooling
31mSpeed up your development flow with Vite
12mVim in the Modern Era: Leveraging a Small Editor for Big Results
10mVite, on demand DX
07mLightning talk: Writing cross-platform editor plugins