Ki Editor surfaced on Hacker News with AST-level editing, but its creator roasted Vim's keymaps, sparking a massive Holy War among developers.
While you guys are busy arguing whether VSCode is a bloated Electron memory hog or if Neovim is just for masochists, a wild challenger has appeared on Hacker News: Ki Editor. This isn't your grandfather's text editor. It doesn't just push plaintext around; it operates directly on the AST (Abstract Syntax Tree). Spicy, right? But the real drama started when the creator decided to poke the bear and roast the Vim ecosystem.
The creator of Ki groups editors into three buckets: the orthodox ones focused on looks (VSCode), modal editors (Vim), and "rethinking the modal approach" (which, conveniently, is Ki). The main selling point here is "First-class syntactic selection." Instead of dragging a mouse or moving by characters like a caveman, you select logical code blocks directly.
Sounds like a cool innovation, but the author took it a step further by officially roasting Vim and Helix keymaps. They called the standard Vim bindings unexplainable, stating there's no logical categorization behind uppercase/lowercase or bracket bindings. So, they invented their own "superior, logical" keymap. Shots fired.
You can't just insult muscle memory and expect peace. The comment section immediately devolved into the classic editor Holy War:
1. The Triggered Vim Chads: One Vim defender immediately fired back: "Vim bindings make total sense! I feel like I'm talking to the editor!" This guy went on to compare the Ki creator to someone who only drives automatic and cries when they see a manual stick shift. To add insult to injury, he dropped a hot take: "Multi-cursor is a useless VSCode feature. Just use Search/Replace and macros like a real dev."
2. The JetBrains Pragmatists:
Users of JetBrains IDEs (IntelliJ, etc.) laughed off the hype. To them, "syntactic selection" is just the legendary Ctrl + W (Expand Selection) they've been using for a decade. Neovim users also chimed in, pointing out that tree-sitter already handles incremental selection perfectly without needing a whole new editor.
3. The Sweaty Plugin Devs:
Someone inevitably asked: "Why not just write a Vim plugin?" Well, some poor souls are actually trying to build ki-bindings.nvim. But here's the catch: Neovim doesn't natively support Ki's concept of "Selection Mode." Worse, Ki uses the Kitty keyboard protocol for momentary layers (e.g., holding c and k simultaneously to duplicate a line). Trying to port this to Neovim requires core architectural changes, leaving devs hacking together cursed workarounds.
4. The Emacs Neckbeards: "All of the above. Which is Emacs." Because of course, any feature you can imagine already has an Emacs package written in Lisp from 1985.
Innovation in developer tooling is always a net positive. AST-based editing definitely seems to be the future for safer, faster refactoring. Thankfully, someone already built a VSCode extension for Ki, so you don't have to install a standalone editor just to satisfy your curiosity.
But let's be real: asking developers to throw away a decade of deeply ingrained muscle memory just to learn a new "logical" keymap is a tall order. Feel free to play around with it on the weekend, but when Monday morning comes, you'll probably crawl back to your trusty old setup to actually ship code and get paid.
Sauce: Hacker News
