Four prevailing themes in the discussion
| # | Theme | Key points & representative quotes |
|---|---|---|
| 1 | Key‑binding coherence & learning curve | “As you can see, there's no single logical categorization for these keymaps… they are either lowercase‑uppercase, normal‑alt, left‑right bracket, or outright unexplainable.” – worksonmine “I think you’re touching on it… stop trying to memorize shortcuts and start thinking in terms of what you want to achieve.” – davidee |
| 2 | AST‑based (syntactic) editing vs. plain‑text editing | “First‑class syntactic modification… Notice the comma between the current and the next node is also deleted.” – hou32hou “I still think their point about search and replace still stand… I make most my edits with regex in neovim… I feel this is the superior paradigm.” – cassepipe |
| 3 | Extensibility & ecosystem trade‑offs | “Emacs is a general‑purpose programming environment… Vim is a text editor… not the same thing.” – umanwizard “Neovim is 71.9 % Lua or VimScript… can you at runtime modify the NeoVim core functions?” – antiframe |
| 4 | Practical usability & adoption barriers | “I’m a quick typist… I can just blat through the changes by hand on the rare occasion… I don’t work on giant line‑of‑business apps.” – marssaxman “I have a Dvorak layout… it’s plainly broken… you end up feeling pretty dumb.” – SloopJon |
These four themes capture the bulk of the conversation: how keybindings feel, whether AST‑centric editing is worth the shift, how the editor fits into existing ecosystems, and the real‑world hurdles people face when trying to adopt a new tool.