IdeaWell

Project ideas from Hacker News discussions.

Vim 9.2

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Wayland vs. X11 support
The release announcement is greeted with excitement about full Wayland UI support, but many users fear that dropping X11 would leave BSDs without a viable desktop stack.

“Full support for the Wayland UI” – jmclnx
“I really hope they never deprecate X11 support” – jmclnx

2. Vim ↔ Neovim and the scripting language debate
The community is split over whether Vim should stay focused on stability and VimScript or adopt Neovim’s modern architecture and Lua‑based plugin ecosystem.

“Neovim has a fundamentally better architecture and healthier ecosystem” – logicprog
“Lua is #2 behind JavaScript/TypeScript when it comes to scripting language LSP stuff” – jitl

3. AI‑powered editing workflows
A growing number of users are experimenting with AI assistants inside Vim/Neovim, seeing them as a way to keep the lightweight editor competitive with full‑blown IDEs.

“I made a vim extension where you describe the edit/action you want in natural language” – user3939382
“Copilot works well” – guerrilla
“AI makes advanced IDE features less relevant (or, more precisely, much easier to ignore or work without)” – qsort

These three threads—graphics‑stack support, the Vim/Neovim divide, and AI integration—dominate the discussion.

🚀 Project Ideas

VimL2Lua: Automated Migration & Linting Tool

Summary

  • Converts legacy VimL scripts to Lua, easing migration to modern Neovim.
  • Provides linting, type‑checking, and refactoring suggestions to reduce runtime errors.
  • Bridges the learning gap for developers who prefer Lua but maintain VimL codebases.

Details

Key Value
Target Audience Vim/Neovim plugin authors, maintainers of legacy VimL scripts
Core Feature VimL parser → AST → Lua code generator + static analysis
Tech Stack Python 3, tree‑sitter VimL grammar, mypy‑style type system, optional Rust for performance
Difficulty Medium
Monetization Hobby

Notes

  • Users lament “VimL is daunting” and “Lua is preferred” (e.g., freedomben, jitl).
  • A tool that automates migration and catches bugs would reduce friction and encourage adoption of Lua.
  • Could spark discussion on best practices for migrating large codebases.

VimAI Hub: Unified AI Integration Framework

Summary

  • Central framework that abstracts multiple AI providers (OpenAI, Claude, OpenRouter, etc.) for Vim/Neovim.
  • Offers chat, autocomplete, natural‑language command generation, and watch‑mode integration in a single plugin.
  • Simplifies plugin development by providing a consistent API and configuration.

Details

Key Value
Target Audience Vim/Neovim users, plugin authors, AI enthusiasts
Core Feature Provider‑agnostic AI client, chat UI, autocomplete engine, watch‑mode support
Tech Stack Rust (core engine), Node.js/Python bindings, TUI (curses/termion), optional WebSocket for real‑time
Difficulty High
Monetization Revenue‑ready: subscription for premium model access (e.g., higher token limits)

Notes

  • Commenters highlight fragmented AI plugins and desire for “watch‑mode” (e.g., troyvit, user3939382).
  • A unified framework would reduce duplication and lower the barrier to entry for AI‑powered editing.
  • Potential for community contributions and plugin ecosystem growth.

Vim MultiCursor: Native Multi‑Cursor Support

Summary

  • Adds true multi‑cursor editing to Vim without relying on external plugins.
  • Provides intuitive keyboard shortcuts, visual feedback, and minimal performance impact.
  • Addresses the frustration of “abandoned” multi‑cursor plugins and the need for a native solution.

Details

Key Value
Target Audience Vim users who need multi‑cursor for refactoring, bulk edits, or IDE‑like workflows
Core Feature Native multi‑cursor API, visual markers, integrated with existing Vim motions
Tech Stack Vim9Script + optional C extension for performance, minimal dependencies
Difficulty Medium
Monetization Hobby

Notes

  • Users like LexiMax and sejje express a strong desire for native multi‑cursor support.
  • Existing plugins are abandoned or lack features; a native implementation would be a game‑changer.
  • Could spark discussion on Vim’s extensibility and future feature roadmap.

Read Later