I read here that the community decided over three years ago on restricting the subject-mater material. There were no dissenting views. Moreover, the Area51 discussions also lack any dissenting views from the now dominant opinion. The FAQ has only this to say,
Please limit your questions to specific queries about members of the Vi and Vim family of editors
To summarize, most of these discussions have assumed a definition of "vim ecosystem" as being,
- A text-editor
- That descends from vi/vim.
For me, that's a very narrow definition.
As a thought experiment,
- If some of the code was borrowed directly from Vim and integrated into the browser, would the browser then be on topic here?
- If Vim was directly compiled to Web Assembly and you ran it on a web page would it be on topic here?
- If something targets vim users, and is made possible only through extension should it be on topic here like VRoom, Vimium, or Surfing Keys?
I don't just use VI, I use other utilities that focus primarily on VIM-keybindings, and I'm interested in spreading these keybindings and this object-modifier syntax to other aspects of the computer-interface. I believe that Vim creates people like me, and the popularity of these tools speaks to that. I think this site would be better if it made an effort to cater to #VimLife or whatever, and not just the editor.
If you ask me what makes Vi and Vim unique and a better method to establish subject matter boundary for the site, I would prefer to differentiate on,
- Software created for the goal of Vi-like keybindings.
- A difference between insert and non-insert (edit/browse/navigate etc) mode.
While of course leaving all the things currently on-topic, on-topic.
This would immediate make the following types of software on topic,